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, idempotentHint, and destructiveHint, so the description needs less behavioral disclosure. It adds meaningful conditional details: authenticated:true with empty pending[] when all providers are connected, and connect_url plus per-install URLs when credentials are missing. No contradiction with annotations.
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 sentences convey the action and both important conditional outcomes without filler. The main behavior is front-loaded, and each clause adds necessary information.
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 parameterless status tool with no output schema, the description covers the all-connected and missing-credential cases well. It could more explicitly address partial-connection states, but nothing blocks an agent from calling it correctly.
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, so the schema carries no input burden and the baseline is 4. The description appropriately spends its effort on output states rather than parameter meaning.
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 opens with 'Returns connection status and URLs,' giving a specific verb and resource. It then clarifies the two key output states, fully connected versus missing credentials, which distinguishes it from the sibling `authenticate` action.
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 provides clear usage context: call it to check connection status and obtain connect URLs when providers are missing. However, it does not explicitly mention alternatives or say when not to use it, such as when the agent should call `authenticate` instead.
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.
Many tools are near-duplicates, such as iclips_financial_entries_get/list, iclips_pieces_get/list, iclips_pieces_write_create/update/checklist, and iclips_workflow_templates_get/list, all sharing essentially the same description. authenticate and connect also overlap on session/connection status, so an agent must rely on brittle naming conventions rather than clear semantic boundaries.
The iClips tools mostly follow iclips_<resource>_<action>, but the server mixes noun-only names like iclips_financial_accounts and marketplace, camelCase platform names like toolkit_info and show_version, and artificial get/list flattened duplicates. The pattern is only predictable within a subset of the tool list, not across the entire server.
At 30 tools, the set is over-inflated for its actual scope: most are flattened get/list or write-action variants of roughly a dozen underlying iClips operations, plus six unrelated platform utilities. The domain could be cleanly served in about half this many tools without losing functionality.
Jobs and pieces have reasonable CRUD coverage, but there is no client/group or destination master lookup even though clientId is required to create a job and destination_id filters financial entries. Job pieces and tasks also lack delete operations, and financial categories are not enumerable, leaving noticeable dead ends for common workflows.