Support for recurring tool calls
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start with client.py at lines 99-102 in the linked quickstart resource and inspect the recurring anthropic.messages.create calls. Determine whether available tools are supplied on each call, then define the expected recurring-call behavior before making a change. The issue is done when the client consistently handles tools during recurring calls.
Written by the indexing model from the issue text.
Description
Should we provide available tools to the model during recurring anthropic.messges.create calls?
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 680
- Avg merge
- 3d 58m
- Merged PRs (30d)
- 9
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from modelcontextprotocol/quickstart-resources
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
modelcontextprotocol/quickstart-resources#46 · 1 comment ·
All issues in modelcontextprotocol/quickstart-resources
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
safetrustcr/dApp-SafeTrust#426 ·
-
area:workflow bug ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
fil-donadoni/tolaria#4409 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Fission-AI/OpenSpec#1960 ·
-
Add dependabot Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
corsairdev/corsair#1764 ·