huggingface / huggingface/mcp-course
request exampe - "arguments" field - confusing
- Dominant language
- MDX
- Stars
- 918
- Forks
- 255
- PR merge metrics
- No merged PRs in 30d
Description
I do not understand the "arguments" field in the JSON-RPC request example
https://huggingface.co/learn/mcp-course/unit1/communication-protocol
`{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "weather",
"arguments": {
"location": "San Francisco"
}
}
}`
I thought that the "method" field contains the name of the method to call. Yes, it is a very obscure name for a method "tools/call", so I have doubts.
I checked https://www.jsonrpc.org/specification#request_object and there is no "arguments" in the examples and "method" really contains the name of the method-to-be-called".
So I can not imagine, what this "arguments" field is for. I rather think this would be enough:
`{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"location": "San Francisco"
}
}`
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the request example on the linked MCP course communication-protocol page, then compare its explanation with the JSON-RPC request-object specification linked in the issue. Clarify the purpose and scope of the nested "arguments" field and revise the example or surrounding text so the relationship between the method and its parameters is unambiguous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100