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 establish readOnlyHint, idempotentHint, and destructiveHint. The description adds concrete behavioral detail: it returns authenticated:true with empty pending[] when all providers are connected, and connect_url plus per-install URLs when credentials are missing. This goes beyond 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. The core action is front-loaded, and the conditional return behavior is stated compactly in the second sentence.
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 zero-parameter status tool, the description explains the key return scenarios: all connected vs. missing credentials. Minor ambiguity exists around partial connection states, but the core behavior needed to invoke the tool correctly is present.
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 accepts zero parameters, so there are no parameter semantics to document. Schema coverage is already complete with an empty properties object, and no additional input guidance is needed.
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?
Description opens with a specific verb ('Returns') and resource ('connection status and URLs'), immediately identifying the tool's purpose. It also distinguishes itself from sibling 'authenticate', which is an action rather than a status/URL inspection.
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 this tool is used to inspect connection state, with conditional behavior for connected vs. missing credentials. However, it does not explicitly state when to prefer this tool over siblings like authenticate or toolkit_info, nor does it name 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 calculo_* tools are largely distinct by legal domain, but several share the same underlying correction/juros mechanics (e.g., calculo_atualizar, calculo_aluguel, calculo_pensao, calculo_trabalhista). Platform tools add further boundary confusion: marketplace includes report_bug, list_tools, and auth-related functionality that overlaps with the standalone report_bug, toolkit_info, and connect tools.
The 16 calculation tools follow a consistent calculo_<domain> pattern, which is good. However, the remaining tools mix bare verbs (authenticate, connect), nouns (marketplace), and verb_noun phrases (report_bug, show_version, toolkit_info), creating two distinct naming conventions within the same server.
At 22 tools, the set is on the heavy side of the borderline range. The domain calculators are individually justified, but adding six platform-level tools — including the very broad marketplace tool — makes the overall surface feel bloated for a server whose apparent purpose is judicial liquidation calculation.
The calculation tools cover a wide range of judicial liquidation scenarios: general debt updating, rent, alimony, labor, FGTS, bank contract revision, INSS restitution, RMC/RCC, criminal sentencing, prisoner progression, pension RMI, contribution time, and asset division. Minor gaps exist — such as a dedicated standalone honorários calculator or a more explicit precatório/RPV tool — but calculo_atualizar largely covers general monetary updating.