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 behavioral specifics about return values in different states (authenticated and pending arrays, connect_url presence), which complements the 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?
The description is two sentences, concise, and front-loaded with the core purpose. Every sentence adds value: the first states what it returns, the second details conditional behaviors.
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 the tool has no parameters, no output schema, and clear annotations, the description is complete for an agent to understand what it does and what it returns. The conditional logic is clearly explained.
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?
The tool has zero parameters, and schema coverage is 100% (empty schema). The description explains the output semantics, which is more relevant than parameter details. With no parameters, the baseline of 4 is appropriate.
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, and specifies the behavior in different scenarios (all providers connected vs. missing credentials). It distinguishes from siblings like 'authenticate' and other CRUD tools.
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 implies usage for checking connection status, but does not explicitly state when to use it versus other tools like 'authenticate' or list tools. However, given the clear purpose and sibling context, the intended usage is apparent.
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.
Every tool maps to a distinct resource-action pair (e.g., leads_create vs businesses_create). Even nested tools like leads_activities_list are clearly scoped from general activities_list. No two tools appear to do the same thing.
All resource tools follow the exact pattern 'datacrazy_<resource>_<action>' with actions being create, get, list, patch, update, delete, plus a few composite verbs like finish_create or actions_win_create. The naming is uniform and predictable.
70 tools is far beyond the usual 3-15 range for an MCP server, making it overwhelming and unwieldy for agents. Although the scope is broad (full CRM), the sheer count exceeds the recommended threshold for effective tool discovery.
Most resources have full CRUD coverage (leads, activities, tags, lists, products, businesses, business_loss_reasons). Some gaps exist: attendants only have get/list, conversations lack delete/update, and pipelines are read-only. These are minor and workable, but not complete lifetime coverage.