Need a summary of your development activity for a specific period? Fetch one by providing the period type and start date. Returns null if none exists.
Fetch a single pre-built summary by period type and start date. Returns null if no summary exists for that period.
| Name | Required | Description | Default |
|---|---|---|---|
| period_type | Yes | ||
| period_start | Yes | YYYY-MM-DD start date of the period |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, description covers return of null if not found, but does not explicitly state read-only nature or other behavioral traits.
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?
Two sentences, front-loaded with purpose, no waste. Efficiently communicates essential information.
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?
Simple tool with two params and no output schema; description covers purpose and return type but lacks usage guidance. Adequate but not complete.
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 50%; description only restates 'period type and start date' without adding meaning beyond schema. Enum and format are already clear from schema.
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?
Description clearly states 'Fetch a single pre-built summary by period type and start date' with specific verb and resource, and distinguishes from sibling 'list_summaries'.
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 on when to use this tool versus alternatives like 'list_summaries' or other search tools. Lacks context for when-not-to-use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/pavelpilyak/devrecall'
If you have feedback or need assistance with the MCP directory API, please join our Discord server