Check whether a data access request would violate aggregate rate limits by evaluating current access and record counts against window parameters and burst limits.
Check if a data access would violate aggregate rate limits.
| Name | Required | Description | Default |
|---|---|---|---|
| agentId | Yes | ||
| sourceId | Yes | ||
| windowMs | No | ||
| burstLimit | No | ||
| lastAccessMs | Yes | ||
| windowStartMs | Yes | ||
| currentAccessCount | Yes | ||
| currentRecordCount | Yes | ||
| maxAccessesPerWindow | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description should disclose behavioral traits. It implies a read-only check but does not explicitly state safety, side effects, or required permissions.
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?
A single concise sentence of 9 words efficiently conveys the purpose, though it lacks detail.
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 9 parameters with no schema descriptions and no output schema, the description is severely incomplete; it only covers purpose.
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?
The description adds no information about the 9 parameters; schema description coverage is 0%, so the description should compensate but does not.
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 verb 'Check' and the resource 'aggregate rate limits,' specifying exactly what the tool does. It is distinct from sibling check tools.
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; no context or exclusions provided.
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/aeoess/agent-passport-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server