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, destructiveHint=false, and idempotentHint=true, covering the safety profile. The description adds value by specifying what information is returned (installed MCPs, statuses, accounts, catalog counts), giving more behavioral detail beyond the annotations. 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?
The description is a single, well-structured sentence that immediately states the tool's purpose and enumerates the returned data. No extraneous words, front-loaded with the core action, and easy to parse.
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 and no output schema, the description covers the necessary context by listing the types of information returned. It adequately informs the agent of what to expect, though it does not specify the exact format or structure of the response. Still, it is sufficient for a simple read-only state inspection.
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 baseline score is 4. The description does not need to elaborate on parameters, and the purpose is self-contained. It effectively communicates what the tool returns without any parameter explanations.
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, listing specific components (installed MCPs, connection status, accounts, catalog tool counts). It distinguishes itself from sibling tools like show_version or connect by focusing on overall state rather than version or actions.
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 toolkit status, but does not explicitly contrast with alternatives or state when not to use it. However, the context is evident from the tool's purpose and the sibling list, so it provides clear context without explicit exclusions.
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 tiny_* tools are clearly distinct by resource and action, but the generic platform tools blur together: marketplace also handles report_bug, install/uninstall, token/connect links, and toolkit state, overlapping with authenticate, connect, report_bug, and toolkit_info. An agent could easily call marketplace for something a dedicated tool already covers, or confuse connect with authenticate.
The Tiny ERP tools follow a clean verb_noun pattern (tiny_list_orders, tiny_get_product, tiny_create_contact), but the platform tools use short unprefixed verbs (authenticate, connect, marketplace, report_bug, show_version, toolkit_info). Two internally consistent naming schemes coexist, so the overall set feels mixed rather than chaotic.
At 20 tools, the count is borderline heavy and mixes two distinct concerns: Tiny ERP operations and mcp.ai platform administration. The ERP tools are each reasonably scoped, but the generic tools could likely be consolidated, especially marketplace, which already absorbs several capabilities.
The ERP surface is heavily read-oriented: contacts, orders, invoices, products, payables, and receivables all support list/get, but only contacts have a create operation. There are no update/delete operations for any entity and no way to create orders, invoices, or products, which creates significant dead ends for real business workflows.