Retrieve your current Accelo API rate limit status, including remaining requests, total limit, and reset time, to monitor usage and prevent hitting the 5000 requests per hour cap.
Get current API rate limit status.
Returns the remaining requests, total limit, and reset time. Accelo allows 5000 requests per hour per deployment.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It usefully discloses the quota (5000 requests/hour per deployment) and the return contents, but omits whether this call itself consumes the quota, auth requirements, or per-deployment scoping behavior.
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?
Three short, front-loaded sentences with no filler: what it does, what it returns, and the quota fact. Every sentence earns its place.
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?
There is no output schema, but the description enumerates the return fields (remaining requests, total limit, reset time) and the quota, which is sufficient for a 0-param read tool. Only the quota-consumption question remains open.
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 tool takes no parameters, which is the baseline-4 case. The description correctly implies a zero-argument call with no filtering options.
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?
States a specific verb and resource: 'Get current API rate limit status.' No sibling tool overlaps with this function, so the agent can immediately place it. The scope is exact and unambiguous.
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?
The purpose implies when to use it (checking remaining quota before a burst of calls), but the description never states a triggering condition or names any alternative. For a self-evident diagnostic tool this is acceptable but not explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.