Describing function parameters and result with dynamically generated tools
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 57/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- csharp
- Domain
- backend-api-design
Research direction
Start with McpServerTool.Create and its McpServerToolCreateOptions, SchemaCreateOptions, and ParameterDescriptionProvider APIs; compare their behavior with KernelFunctionFactory.CreateFromMethod, which the issue cites. Work out how parameter and return value descriptions are supplied for dynamically generated tools, then provide a simple sample showing the supported approach.
Written by the indexing model from the issue text.
Description
Let's say I create a tool with McpServerTool.Create(MethodInfo, object, McpServerToolCreateOptions) function, what is the best way to describe parameters and result?
Are the only ways to use McpServerToolCreateOptions.SchemaCreateOptions or/and ParameterDescriptionProvider ( But then how does one describe return value - OutputSchema?)?
Or is there a way to pass descriptions through a property?
I mean like Microsoft.SemanticKernel.KernelFunctionFactory.CreateFromMethod where there is a parameters parameter when one can describe parameters and a returnParameter parameter for result.
A simple sample would be appreciated.
- Dominant language
- C#
- Stars
- 4.6k
- Forks
- 849
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 24
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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/csharp-sdk
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
modelcontextprotocol/csharp-sdk#2031 ·
Maintainers usually reply within 1 day
-
Static resources whose URIs differ only in the fragment or user info collapse into onePossibly taken @halter73 claimed this 10 days ago. OpenP2
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
modelcontextprotocol/csharp-sdk#1970 · 4 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
POST /mcp with a missing or unparseable Content-Type returns HTTP 500 instead of a 4xxPossibly taken @halter73 claimed this 10 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
modelcontextprotocol/csharp-sdk#1966 · 5 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Reserved URI-template expansion throws for supplementary Unicode charactersPossibly taken @tarekgh claimed this 3 days ago. OpenP3
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
modelcontextprotocol/csharp-sdk#1913 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
ClaimsPrincipal parameter injection sample requestPossibly taken @utsavjain2809 claimed this 48 days ago. Openhelp wanted P3
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
modelcontextprotocol/csharp-sdk#1899 ·
Maintainers usually reply within 1 day
All issues in modelcontextprotocol/csharp-sdk
Similar issues
-
CLI: stale build hint, non-gofmt autocomplete output and a leftover `--revit=<year>` in the docsOpenCommand Line Utility (CLI)
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pyrevitlabs/pyRevit#4217 ·
Maintainers usually reply within 1 day
-
area: ui bug ready
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
account bug effort:S P2
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nightscout/nocturne#3745 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
grate-devs/grate#969 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
jsboige/CoursIA#27768 · 2 comments ·
Maintainers usually reply within 1 day