Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.
| 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 and destructiveHint=false. The description adds value by detailing the included state information (installed MCPs, connection status, accounts, catalog counts), which goes beyond the raw annotation flags. No contradictions.
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?
A single sentence that front-loads the purpose ('Returns the current toolkit state') and lists key output components without any fluff. 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?
With no output schema, the description must convey return contents, and it does list the main elements. It could hint at the data structure (e.g., whether it's a nested object or list), but given the simple status tool, the coverage is adequate.
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?
Tool has zero parameters, so the description need not explain them. The schema is empty with 100% coverage, and the baseline for zero-param tools is 4. The description correctly omits parameter discussion.
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 uses a specific verb 'Returns' and clearly specifies the resource: 'current toolkit state' with enumerated details (installed MCPs, connection status, accounts, catalog tool counts). This distinguishes it from siblings like show_version and authenticate.
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 inspecting the overall toolkit state but does not explicitly contrast with alternatives. Given the simple zero-parameter nature, the context is clear enough, though explicit exclusions are absent.
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.
Several tools are duplicated with nearly identical descriptions, distinguished only by a '[Flattened action]' footnote (e.g. evo_activity_list vs. evo_activity_schedule, evo_member_get vs. evo_member_list, evo_prospect_write_create vs. evo_prospect_write_update). An agent would struggle to pick the correct one without parsing fine-print labels. authenticate and connect also blur the auth boundary.
The EVO tools use a rough 'evo_<noun>_<action>' pattern but mix verb positions and styles: evo_member_get, evo_list_accounts, evo_activity_schedule, evo_sales_create, evo_bank_accounts. Platform tools like authenticate, connect, report_bug, and marketplace abandon the evo_ prefix entirely, and the giant marketplace tool follows no naming convention.
26 tools is above the 15–25 'heavy' band, and several are redundant flattened variations that should be merged. The set also mixes domain-specific EVO tools with unrelated platform utilities (marketplace, toolkit_info, report_bug), inflating the count without coherent coverage.
The domain is gym management (members, activities, prospects, sales, receivables), but the surface has major gaps: no member create/update/delete, no activity-create or schedule management, and only partial write operations elsewhere. Some tools contain unresolved 'PROBE' prompts, indicating unfinished endpoints that agents cannot reliably use.