saldo_creditos
Saldo de créditos disponible de tu API key y consumo del mes. Gratis.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
empresas
TDQS
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries the burden. It discloses the tool is a read operation and 'Gratis' (free) indicating no credit consumption. This is adequate for a simple quota check.
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?
The description is a single concise sentence in Spanish. It is front-loaded with the purpose and contains no wasted words.
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?
For a simple tool with no parameters or output schema, the description provides the essential purpose and notes it's free. It could specify output format, but overall adequate.
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, so schema coverage is 100%. The description adds meaning by specifying the tool returns credit balance and consumption, compensating for the lack of output schema.
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?
The description clearly states the tool retrieves the credit balance and monthly consumption for the API key. It distinguishes itself from sibling tools which are all search/profile tools.
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?
The description implies usage for checking credits before API calls, but lacks explicit guidance on when to use vs alternatives or prerequisites.
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
A4.1/5.0
Disambiguation5/5
Each tool targets a distinct entity or action: searches for people, companies, importers, and tenders are clearly separated, as are company and person detailed profiles, credit balance, and autocomplete. The two overlapping-looking tools (buscar_empresas and sugerencias) differ in purpose: full search vs. lightweight autocomplete, so no real ambiguity exists.
Naming Consistency4/5
Tool names follow a clear pattern: buscares use verb_noun, fichas use noun_noun, and saldo_creditos/sugerencias are standalone nouns. This is mostly consistent and predictable, with minor deviation from a strict verb_noun pattern.
Tool Count5/5
With 8 tools, the server is well-scoped for its purpose of retrieving Argentine business data. It covers multiple search domains, detailed profiles, account management, and autocomplete without excessive fragmentation or unnecessary tools.
Completeness4/5
The core domain is well covered: search for companies, people, importers, and tenders, plus detailed profiles for companies and people. A minor gap is the lack of detail views for individual importers or tenders beyond search results, but agents can typically work around this with the existing search capabilities.