get_usage
Get current billing period usage vs quota for this API key.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Algenta MCP Server
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.6/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must cover behavioral traits. It only reiterates the purpose without disclosing any side effects, authentication requirements, rate limits, or data freshness. Agent learns nothing beyond the basic function.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence that is direct and efficient. No unnecessary words, front-loaded with the key action (Get) and resource. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no parameters, no output schema, and a simple retrieval task, the description covers the essential: what is retrieved and its scope. Missing details like authentication context, but implied by 'for this API key'.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters exist (0 params, schema coverage 100%), so baseline is 4. Description adds no parameter info, which is acceptable since no parameters are needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the verb 'Get', the resource 'current billing period usage vs quota', and the scope 'for this API key'. It distinguishes from sibling tools like get_billing_info by focusing specifically on per-API-key usage.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
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 (e.g., get_billing_info, get_limits). The description only states what it does but does not help an agent decide between similar tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
C2.7/5.0
Disambiguation4/5
Most tools target distinct resources or actions, but there is some overlap (e.g., run_repository_fix vs run_repository_pipeline vs simulate_repository) that could cause confusion. Overall, descriptions help differentiate.
Naming Consistency3/5
Tool names are primarily snake_case with a verb_noun pattern, but there are inconsistencies (e.g., single-word verbs like 'simulate', 'tokenize', and mixed prefixes like 'preview_', 'product_'). The pattern is readable but not uniform.
Tool Count1/5
With 140 tools, the server is extremely over-scoped for typical MCP usage. This overwhelms agents and suggests poor separation of concerns, likely violating the principle of minimal tool surfaces.
Completeness4/5
The tool set covers a wide range of functionalities including data onboarding, simulation, decisions, repository management, and admin operations. Minor gaps exist (e.g., no update_agent_run), but core workflows are well-supported.