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 indicate readOnly, idempotent, and non-destructive. The description adds meaningful context by specifying exact return fields ('authenticated:true', 'empty pending[]', 'connect_url', per-install URLs) for each state. This enriches the behavioral model without contradicting 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 concise sentences with front-loaded purpose. The conditional logic is compact and each clause delivers useful information without fluff.
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?
For a simple read-only status tool with no output schema, the description covers all relevant behaviors: both states (connected/missing credentials) and the URLs returned. It is complete for an agent to decide when and what to expect.
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 trivially 100%. Baseline for 0 params is 4; the description does not need to compensate and doesn't mislead.
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 and resource. It also describes conditional outcomes (authenticated:true vs connect_url), making its purpose unmistakable and distinct from sibling tools like authenticate.
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 when to use: when needing connection status. It provides clear scenarios for both connected and missing credentials states. However, it does not explicitly distinguish from alternative tools like authenticate or say when not to use.
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 are mostly distinguishable: the domain query is unique, and platform tools like authenticate, connect, and report_bug have clear roles. However, connect and toolkit_info both report connection status, and marketplace handles a wide range of actions, causing minor overlap.
Names mix verbs (authenticate, connect), nouns (marketplace), and underscores with inconsistent ordering (report_bug vs toolkit_info vs situacao_eleitoral_consultar). There is no uniform verb_noun pattern across the set.
Seven tools is a reasonable count for a platform wrapper with one domain integration. Each tool serves a purpose, though show_version is trivial and marketplace is oversized.
The domain surface is minimal—only a single consult operation for electoral status, which is appropriate for a read-only public query. The platform tools extend capability via the marketplace, but for a dedicated TSE server, additional operations like batch or status checks are missing.