Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds useful behavioral context about response structure (authenticated vs connect_url), providing value beyond annotations without contradiction.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences with no fluff. The key information is front-loaded, and every sentence serves a purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given zero parameters and a simple status check function, the description completely explains the tool's behavior and return values. No missing information for effective use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters exist, so schema coverage is 100%. The description does not add parameter-level details, but with zero parameters, a baseline score of 4 is appropriate as nothing is missing.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns connection status and URLs, with specifics about response states. However, it does not explicitly differentiate from the sibling tool 'authenticate', missing an opportunity to clarify distinct purposes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like 'authenticate'. The description implies a status-check role but lacks explicit when-to-use or when-not-to-use instructions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.