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?
The description goes beyond the annotations (readOnly, idempotent, non-destructive) by detailing the exact pieces of information returned (installed MCPs, connection status, accounts, catalog tool counts). This adds valuable behavioral context, ensuring the agent knows what to expect without needing to invoke the tool.
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 a single, concise sentence that efficiently lists the return content without unnecessary detail. It is well-structured and directly to the point.
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?
There is no output schema, but the description fully describes what the return value includes, making the tool's purpose and results clear. It is complete for a simple informational tool without needing additional explanation.
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 no parameters, and the schema coverage is complete (100%). Since there are no parameters to describe, the description cannot add value in this dimension. Per the rubric, the baseline for high coverage is 3, so this score 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 the current toolkit state with specific details (installed MCPs, connection status, accounts, catalog tool counts), using a specific verb 'Returns' and a distinct resource. It distinguishes itself from sibling tools by focusing on toolkit-level information rather than individual note operations.
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 retrieving overall toolkit status, which is self-explanatory. It does not explicitly mention alternatives, but given the nature of the tool as a status/info aggregator, alternatives are not obvious. Lacks explicit when-to-use guidance, but it's adequate.
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.
The keep_* tools are clearly distinct with verb_noun patterns, and the platform tools (authenticate, connect, marketplace, etc.) serve separate functions. No two tools appear to do the same thing, though the mix of Keep and platform tools could cause an agent to briefly confuse context.
The keep_* tools follow a consistent keep_verb_noun pattern, but the platform tools use simple unrelated names (authenticate, connect, marketplace) without the prefix, breaking consistency across the set.
At 30 tools, the server exceeds the recommended range. While the Keep operations are comprehensive, the inclusion of 6 platform management tools inflates the count and makes the surface heavier than necessary for a Keep-focused server.
The Keep tools cover full lifecycle: create/read/update/delete for notes, list items, labels, and collaborators, plus archive/trash/pin and media retrieval. The platform tools add connection and marketplace capabilities. Minor gaps like bulk operations on notes are partially addressed with bulk support fields.