Skip to main content
Glama

Dilligence — certidões de empresas

Ajustar carteira de monitoramento

update_monitor

Muda nome, frequência (diaria, semanal, mensal), certidões ou pausa/retoma (active) uma carteira.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "monitor_id": "<monitor_id>"
    },
    "name": "update_monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
activeNo
certidoesNo
frequencyNo
monitor_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly=false, destructive=false, idempotent=false and openWorld=false, so the safety profile is covered. The description adds genuinely useful behavior by mapping 'active' to pause/resume semantics and framing the call as a partial field update, but it stays silent on whether 'certidoes' replaces or appends, and on permissions/return behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One compact sentence with the mutable fields front-loaded and zero filler. It is efficient, though the terse Portuguese phrasing packs multiple operations into a single clause without structural breakdown.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter partial-update tool with no output schema, the description covers the substantive fields and the pause/resume meaning. What remains missing — the required monitor_id role and the effect of list-valued 'certidoes' — is a modest gap rather than a blocking one.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage the description must carry parameter meaning; it does explain four of the five parameters (including that 'active' toggles pause/resume), which is real added value. However, it never mentions 'monitor_id', the sole required parameter and the target of the update, and leaves the replacement semantics of 'certidoes' ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Muda') plus the resource ('carteira') and enumerates the mutable fields (name, frequency, certidões, active). This clearly separates it from create_monitor, get_monitor and list_monitors, though it never names a sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus create_monitor/rename_diligence, no mention that monitor_id is required, and no stated prerequisites (e.g., ownership, whether the portfolio must be active). Usage is only implied by the verb.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.