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 readOnly, non-destructive, and idempotent. The description adds valuable context about the response states (authenticated:true with empty pending[], or connect_url when credentials are missing), which is beyond what annotations provide.
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?
The description is two sentences, front-loaded with the primary purpose and then providing conditional details. Every word earns its place with no redundancy.
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?
For a simple status-check tool with no parameters and no output schema, the description is complete. It explains both possible states (connected vs. missing credentials) and what the return values will be, so the agent knows exactly what to expect.
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?
There are zero parameters, so the baseline is 4. The description doesn't need to add parameter details, and the schema coverage is vacuously 100%.
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 specific response conditions. It distinguishes itself from siblings like authenticate (which likely initiates auth) by focusing on status checking.
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?
The description gives conditional context by explaining behavior when providers are connected versus when credentials are missing. It doesn't explicitly name alternatives, but the sibling list and the nature of the tool imply it's for checking status rather than performing authentication.
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 purposes, but 'authenticate' and 'connect' both deal with authentication state, and 'marketplace' overlaps slightly with 'toolkit_info' in terms of discovering vs. viewing tools. These pairs could cause initial confusion, though descriptions help.
Names mix English verbs (authenticate, connect, report_bug) with a noun (marketplace) and a Portuguese command (fincen_consultar). There is no consistent verb_noun or noun pattern, making the set feel ad hoc.
With 7 tools, the number is well within the typical range for a platform server. Each tool serves a distinct functional area (auth, status, query, marketplace, bug, version, toolkit), so none feels superfluous.
The platform covers essential operations: authentication, connection status, tool discovery/execution, bug reporting, version info, and toolkit state. The FinCEN-specific side is minimal (one query tool), but the marketplace allows extending coverage, so the surface is reasonably complete.