get_billing_status
Idempotent
Return current plan, subscription status, and remaining credits.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
convertfilefast
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- Added
TDQS
A4.1/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate idempotent and open world; description adds return details but no extra behavioral context beyond what annotations imply.
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 with no unnecessary words, directly conveying purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given zero parameters and presence of output schema, the description fully captures what the tool does.
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; description adds value by stating output fields without needing to explain inputs.
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 states 'Return current plan, subscription status, and remaining credits' with a specific verb and resource, clearly distinguishing from sibling tools that handle billing actions.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implied usage as a read-only status check, but no explicit when/ when-not or alternative guidance provided.
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
A3.6/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose, covering different file operations (compress, convert, extract, merge, split, etc.) and billing management. No two tools overlap in functionality.
Naming Consistency4/5
Most tool names follow a verb_noun pattern (compress_image, protect_pdf), but a few deviate (images_to_pdf, list_supported_conversions) causing minor inconsistency. The pattern is largely predictable.
Tool Count4/5
17 tools is slightly above the typical well-scoped range, but still reasonable given the breadth of file manipulation and billing operations. Each tool serves a distinct need.
Completeness4/5
The file conversion and PDF manipulation operations are well-covered (compress, convert, extract, merge, split, protect, etc.). The billing tools are complete for subscription and credit management. Minor gaps exist, such as batch operations or image format conversions.