show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Procfy
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description does not add behavioral details beyond what annotations already provide. Annotations declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which fully cover its safe, read-only nature. The description adds no extra context about behavior.
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, complete sentence with no extraneous words. It is front-loaded and effectively communicates the tool's 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, good annotations, and a simple output (version strings), the description is fully adequate. No additional information is 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 tool has zero parameters, and the schema covers 100% of the (nonexistent) parameters. The description does not need to add parameter details. Baseline 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 clearly states that the tool displays current MCP platform and adapter versions. The verb 'Show' and resource 'current MCP platform and adapter versions' are specific and unambiguous. It is distinct from all sibling tools, which focus on authentication, connection, or accounting operations.
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?
The description provides no guidance on when to use this tool or when to prefer alternatives. For such a simple tool, usage context is inherently clear, but explicit guidance is absent.
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
B3.3/5.0
Disambiguation4/5
Most tools have clear, distinct purposes, especially the procfy_list_* tools which each target a different entity. The platform tools (authenticate, connect, marketplace) are also distinguishable. However, the marketplace tool is multi-purpose with different actions, which could cause some confusion, but descriptions help.
Naming Consistency3/5
Procfy-specific tools follow a consistent 'procfy_verb_noun' pattern, but platform tools (authenticate, connect, marketplace, etc.) lack a prefix and mix verb and noun forms (e.g., marketplace is a noun). This inconsistency in naming conventions across the set reduces clarity.
Tool Count4/5
With 16 tools, it's slightly above the ideal 3-15 range, but still reasonable for a domain covering multiple entities (accounts, bank accounts, categories, etc.). The inclusion of platform tools (6) contributes to the count, but they are necessary for the server's operation.
Completeness2/5
The server provides extensive list operations and a create for transactions, but lacks update/delete for transactions and CRUD for other entities (categories, contacts, etc.). No tool for getting individual entities (except transaction and bank account balance) or creating/modifying them. Significant gaps for a full lifecycle.