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 readOnly and idempotent, but the description adds valuable behavioral detail: the two possible outcomes (authenticated:true with empty pending[], or connect_url with per-install URLs) and what triggers each. This goes beyond the structured 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, no filler. The first sentence states the purpose, the second clarifies the conditional output. 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?
Given the tool is parameterless and has no output schema, the description fully explains the expected return values and conditions. Annotations cover safety, and the description covers behavior completely for this simple tool.
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 provides no parameter semantics. Baseline is 4, and description correctly focuses on output behavior rather than params.
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 connection status and URLs, with a specific verb ('Returns') and resource ('connection status and URLs'). It distinguishes itself from sibling 'authenticate' by describing a status check rather than an action.
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 provides clear context on when results differ (all providers connected vs credentials missing), implying it is used to check connection state. It does not explicitly name alternatives or exclusions, but the sibling 'authenticate' is evidently the counterpart for initiating auth.
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.
Most tools have clearly distinct purposes, but authenticate and connect both relate to authentication/connection status, which could confuse an agent. The single domain tool (mandados_prisao_consultar) is clearly distinct from the platform utilities.
Names are lowercase with underscores but mix bare verbs (authenticate, connect), verb+noun compounds (report_bug, show_version), and nouns (marketplace, toolkit_info). The Portuguese name mandados_prisao_consultar breaks the English pattern, resulting in an inconsistent though readable set.
With 7 tools, only one relates to the server's stated domain of arrest warrants; the other six are generic MCP platform utilities. This makes the count inappropriate as the platform tools dilute the server's focus and purpose.
The server offers only a single domain operation (mandados_prisao_consultar) and lacks any other warrant-related operations such as listing, detailed lookups, or historical searches. The platform tools are comprehensive for infrastructure but do not contribute to the domain, leaving the core purpose severely incomplete.