Model-aware tool definitions
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- api
Research direction
Start by reading the existing WebMCP tool definition and schema entry points to see how descriptions and parameters are represented. Then assess where model or model-family context could be provided, and how a default definition would fit. Done means agreeing on an API and behavior for model-specific descriptions, schemas, and parameter descriptions with a fallback.
Written by the indexing model from the issue text.
Description
Different LLMs can behave differently when given the same tool definition.
A tool description and input schema that work well with one model may perform worse with another. One model may select the right tool and arguments, while another may select the wrong tool or generate invalid arguments from the same definition.
WebMCP could support model-aware tool definitions.
description: ({ model, modelFamily }) => {
if (model === "gpt-5.6") {
return "...";
}
if (modelFamily === "gpt-5") {
return "...";
}
return "Search for products.";
},
The exact API is just an example. Developers could return different tool descriptions, schemas, or parameter descriptions based on the model or model family, with a default fallback.
P.S. This is my first contribution to WebMCP!
- Dominant language
- Bikeshed
- Stars
- 4.7k
- Forks
- 328
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 15
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 webmachinelearning/webmcp
-
Say how an agent should weigh annotations that the page wrote about itselfPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
webmachinelearning/webmcp#353 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
webmachinelearning/webmcp#343 · 1 reaction ·
Maintainers usually reply within 1 day
-
Agenda+ i18n-tracker
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
webmachinelearning/webmcp#273 · 3 comments ·
Maintainers usually reply within 1 day
-
a11y-tracker Agenda+
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
webmachinelearning/webmcp#272 · 4 comments · 2 reactions ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
webmachinelearning/webmcp#234 · 5 comments ·
Maintainers usually reply within 1 day
All issues in webmachinelearning/webmcp
Similar issues
-
`github-events` aborts the repository scan when a closed pull's API payload has a null `head`Possibly taken @renyamamoto2026-cmyk claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
zerocracy/judges-action#2823 ·
Maintainers usually reply within 1 day
-
cleanup hacktoberfest priority: low skill: good first issue testing
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
hyperledger-labs/fabric-smart-client#2197 ·
Maintainers usually reply within 1 day
-
[Bug] Unhandled ValueError terminates watchdog thread when GISRC value contains multiple colonsOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
corro-client drops the last byte of a response line that has no trailing newlinePossibly taken @RaphaelFakhri claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
joinrpg/joinrpg-net#5752 ·
Maintainers usually reply within 1 day