hellogithubFetches current trending repositories on GitHub. Use it to discover popular open-source projects.
获取GitHub Trending
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "hellogithub"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| noCache | No |
Changes observed during successful MCP inspections.
v0.1.13Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description bears full responsibility. It only states the high-level action and omits behavioral details such as authentication, rate limits, caching (despite a noCache parameter), or the source of the data (GitHub trending page).
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise (one short phrase), but sacrifices necessary detail. While brevity is positive, the lack of parameter and usage information makes it under-specified.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has 2 optional parameters, no output schema, and many sibling tools, the description is insufficient. It fails to explain the tool's behavior, scope, or how it differs from similar tools.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0% and the description provides zero explanation of the 'limit' or 'noCache' parameters. The agent receives no help understanding their meaning or impact.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action '获取' (get) and the resource 'GitHub Trending', making the purpose straightforward. However, it does not differentiate from sibling tools like 'github' which might have overlapping functionality.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. With over 50 sibling tools, the lack of selection criteria hinders the agent's ability to choose correctly.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.