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, covering safety. The description adds valuable context about the two possible response states (authenticated with empty pending, or connect_url when credentials are missing), going beyond what annotations provide.
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. Every clause adds value, and there is no redundant or filler content.
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?
Without an output schema, the description appropriately explains the tool's return behavior, covering both primary states. This is sufficient for the simple nature of the tool and its zero parameters.
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 schema coverage is effectively 100%. Per the rubric, a 0-parameter tool gets a baseline of 4, and the description adds no param-specific info because none exists, which 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's function: 'Returns connection status and URLs.' It differentiates itself from siblings like 'authenticate' by describing specific output states (authenticated:true vs connect_url), making it distinct.
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 the tool is used to check connection status, but does not explicitly state when to use it versus alternatives or when not to use it. There is no mention of exclusions or alternative tools, so it falls into the 'implied usage' category.
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.
Each tool has a clearly distinct purpose: authentication, connection status, marketplace operations, bug reporting, version display, a specific data query, and toolkit state. No two tools overlap in functionality, and the descriptions make boundaries explicit.
Tool names mix verbs (authenticate, connect), nouns (marketplace), verb_noun compounds (report_bug, show_version, toolkit_info), and a Portuguese-specific name (sintegra_es_consultar). There is no consistent pattern in style or language.
Seven tools is well within the ideal range for a platform management server. Each tool covers a necessary function without redundancies or excessive granularity.
The set covers authentication, connection status, marketplace search/run/install, feedback, version, and toolkit state. Minor gaps exist (e.g., no dedicated prompt library tool), but these are bundled into marketplace, so core workflows are not obstructed.