Skip to main content
Glama
OpenMonetis MCP

OpenMonetis MCP

by Welington98

Revogar conexão

revoke_person_connection
Destructive

Revoke a connected person's access to financial data; requires confirm: true because the action is destructive.

Instructions

Revoga o acesso de uma pessoa conectada. Exige confirm: true (ação destrutiva).

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": {
      "id": "<id>"
    },
    "name": "revoke_person_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
confirmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered structurally. The description adds genuinely new behavioral context by stating that confirm must be true — something the annotation set does not express. It still does not say what access is lost on revocation or whether the connection record itself is deleted.

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

Conciseness5/5

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

Two short sentences with zero padding, and the destructive precondition is stated right after the purpose. Nothing redundant or buried.

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

Completeness3/5

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

For a destructive two-parameter mutation with no output schema and no field-level schema docs, the definition covers the required confirmation gate but omits the consequence of the action (what access is severed, reversibility, permission requirements). It is minimally viable rather than complete.

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?

Schema description coverage is 0%, so the description must carry the load; it does explain the meaning of 'confirm' (must be true, destructive). The 'id' parameter's target (which connection) is left completely implicit, so the compensation is only partial.

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 ('Revoga') and resource ('acesso de uma pessoa conectada'), which is clearly distinct from list_person_connections or create_person_invitation. It stops short of naming the nearest alternative with a similar name (cancel_person_invitation), so the boundary is inferred rather than stated.

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

Usage Guidelines3/5

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

The description conveys the precondition ('Exige confirm: true') which implies the tool is for an intentional destructive, confirmed action. However it never says when to revoke vs. cancel an invitation or when not to use it, leaving the agent to infer usage from the name alone.

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