show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
F360 Finanças
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 the tool as read-only, idempotent, and non-destructive. The description adds that it shows platform and adapter versions, but does not disclose any additional behavioral traits such as caching or network dependency. With annotations present, the burden is lower, and the description provides minimal extra context.
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, front-loaded sentence with no wasted words. It is appropriately sized for such a simple tool.
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, no output schema, and comprehensive annotations, the description is sufficient. It fully explains the tool's purpose without needing additional details about return format or usage context.
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?
There are zero parameters, and the schema coverage is 100%. According to guidelines, baseline is 4. The description does not need to add parameter details.
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 shows current MCP platform and adapter versions, using a specific verb and resource. It distinguishes itself from sibling tools that serve different purposes, such as marketplace or toolkit_info.
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 when to use (to get version info) but provides no explicit guidance on when not to use or alternatives. With sibling tools like toolkit_info that might also provide version-related information, differentiation is lacking.
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.9/5.0
Disambiguation4/5
Most tools are clearly distinct, especially the f360_* family which separates listing, detail, and report generation per resource. However, 'authenticate' and 'connect' both deal with connection state, and 'f360_list_accounts' vs 'f360_listar_planos_contas' could be confused without reading descriptions closely.
Naming Consistency2/5
Naming is inconsistent: generic tools use simple English verbs (connect, show_version), while financial tools mix English (list_accounts) and Portuguese (listar_notas, obter_xml) with inconsistent verb forms and prefixes. The patterns are not predictable across the full set.
Tool Count3/5
At 19 tools, the set is borderline heavy. Six tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) are platform-level utilities unrelated to the financial domain, inflating the count; the remaining 13 financial tools are well-scoped for a read-only reporting API.
Completeness3/5
The financial tools cover listing and detail retrieval for core entities (accounts, notes, people, chart of accounts) and generate/download reports. However, there are no create/update/delete operations, and no getter for accounts or other entities, limiting the surface to read-only reporting.