Get workspace health, including connection state across providers. Pass provider to check one provider's connections.
| Name | Required | Description | Default |
|---|---|---|---|
| provider | No | Optional provider to check connection health for. |
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?
With no annotations, the description must carry the full burden. It mentions the connection state and the provider filtering behavior, but does not disclose return format, side effects, or error scenarios. It adds some behavioral nuance beyond the name, but not much.
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 concise sentences, front-loaded with the main action and a clear optional parameter usage. Every word earns its place.
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 health-check tool with one optional parameter and no output schema, the description is adequate but incomplete. It tells what it checks (connection state) but does not describe output shape or potential response types, which could be relevant without an output schema.
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?
Schema coverage is 100% with a descriptive parameter. The description's 'Pass provider to check one provider's connections' essentially restates the schema's 'Optional provider to check connection health for', adding minimal extra meaning. Baseline 3 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 gets workspace health and includes connection state across providers, which is a specific verb+resource. It does not explicitly distinguish from siblings like workspace_usage, but the reference to connection state is specific enough to understand its purpose.
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 usage context by explaining the optional provider parameter, but does not mention when to use this tool versus alternatives. It implies usage for checking health but lacks explicit when/when-not guidance.
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 clearly distinct purposes, but a few are close: delete_instagram_comment vs hide_instagram_comment overlap (though one is preferred), and get_analytics overlaps with Instagram-specific analytics tools. Overall, the boundaries are generally clear, with only minor potential confusion.
All tool names follow a consistent snake_case verb_noun pattern (e.g., list_accounts, connect_account, upload_asset, cancel_post). There are no deviations in style or grammar, making the naming highly predictable.
With 31 tools, this exceeds the 25-tool threshold for 'too many'. While the broad multi-provider social media domain justifies some breadth, the sheer number makes the surface heavy and potentially overwhelming, pushing the score down.
The tool set covers core workflows well: account connection, scheduling/publishing, post management, analytics, Instagram-specific engagement (comments, messages), asset upload, and workspace health/usage. Minor gaps include no explicit disconnect_account or delete_post, but these are edge cases; the domain is largely covered.
