show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Análise de Crédito PF Completa
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4.1/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and non-destructive. The description aligns with these and clarifies the specific content (platform and adapter versions), but adds no additional behavioral details beyond annotations.
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, direct, no wasted words.
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?
Simple 0-parameter, read-only tool; the statement fully conveys what the user will get (versions). No output schema required.
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?
The schema has zero parameters, so description needs no parameter semantics. Baseline of 4 is appropriate.
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 uses the specific verb 'Show' with a clear resource: 'current MCP platform and adapter versions.' This differentiates from sibling tools like authenticate or report_bug, which target different 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?
No explicit usage guidance or alternatives are mentioned. However, the tool name and description imply its use when version information is needed. There is no when-not-to-use guidance.
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
Disambiguation3/5
The credit analysis tool is clearly distinct, but several platform tools overlap: authenticate, connect, and toolkit_info all deal with connection/auth status, and marketplace is a mega-tool covering many actions. This overlap could cause an agent to select the wrong utility.
Naming Consistency2/5
Names mix English verbs (authenticate, connect), English verb_noun (report_bug, show_version), nouns (marketplace, toolkit_info), and a Portuguese compound (credito_pf_completo_consultar). There is no consistent naming pattern across the set.
Tool Count3/5
Seven tools is within a typical range, but only one tool serves the credit analysis domain; the other six are generic platform utilities. The set feels padded relative to the server's stated purpose.
Completeness4/5
The single credit tool covers the full consultation: cadastral data, score, pending issues, and history. Minor gaps exist (e.g., no direct balance or query history), but the marketplace can handle payment top-ups indirectly.