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?
With annotations already declaring readOnlyHint=true and destructiveHint=false, the description adds behavioral context by describing the conditional response for connected vs. missing-credential states. It does not contradict the 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 with no filler. Each sentence provides distinct information: the general purpose and the conditional outcomes.
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?
The tool is simple (no params), and the description covers the two main states and key fields (authenticated, pending, connect_url). However, it doesn't address a partially-connected state or define 'per-install URLs' fully, leaving a minor gap.
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?
With zero parameters, there is nothing for the description to explain; the baseline of 4 applies. The description correctly focuses on return behavior instead.
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 identifies the resource ('connection status and URLs'), clearly distinguishing it from siblings like 'authenticate' which likely initiates a connection. The state-based explanation further clarifies what the tool reports.
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 does not explicitly state when to use this tool over 'authenticate' or other siblings. It implies a status-checking role but lacks explicit 'use this when...' guidance or 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.
Tools like authenticate, connect, report_bug, and show_version have distinct purposes. However, the 'marketplace' tool is a monolithic mega-tool that bundles search, describe, invoke, install, subscribe, cancel, and prompt-library operations, making it ambiguous which sub-action is intended. The domain-specific 'mpf_amazonia_protege_consultar' also sits awkwardly alongside generic platform tools.
Names are inconsistent: some are single verbs (authenticate, connect), some are nouns (marketplace, toolkit_info), and one uses long snake_case (mpf_amazonia_protege_consultar). There is no coherent naming convention across the set, mixing verb-first, noun-first, and domain-specific styles.
Seven tools is a reasonable number for a platform utility server. The count is not excessive, but the 'marketplace' tool absorbs many responsibilities, which skews the effective scope. A few generic tools (report_bug, show_version) are expected in such a platform.
The server covers authentication, connectivity, marketplace operations (search, invoke, install), bug reporting, versioning, and toolkit status. However, the marketplace tool's monolithic design hides sub-operations, and the domain-specific query tool (mpf_amazonia_protege_consultar) suggests a data source but only exposes one operation. Missing explicit logout or disconnect operations.