Skip to main content
Glama
OpenMonetis MCP

OpenMonetis MCP

by Welington98

Conexões entre pessoas

list_person_connections
Read-onlyIdempotent

Lists active connections between the account holder and other people, from owner or recipient perspective, including status and date.

Instructions

Lista as conexões ativas entre o titular e outras pessoas (perspectiva de dono ou destinatário), com status e data.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_person_connections"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description contributes real extra context by stating that only *active* connections are returned and that each carries status and date, but it says nothing about pagination, ordering, or how the owner/recipient perspective affects results.

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 resource and scope front-loaded and no filler. The trailing 'com status e data' is slightly terse but still earns its place by hinting at returned fields.

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 zero-parameter, closed-world read tool with no output schema, the definition covers what is listed, the filter (active only), and the perspective. It is close to complete; only the shape/ordering of the returned status and date values is left unstated, which is minor here.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The description correctly does not invent parameter detail, though it could have clarified that the perspective (owner vs recipient) is implicit rather than selectable.

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 ('Lista') and a clearly bounded resource ('conexões ativas entre o titular e outras pessoas'), and adds the perspective qualifier (dono ou destinatário) plus the returned fields (status e data). It does not, however, distinguish itself from siblings such as list_person_invitations, list_person_settlements or revoke_person_connection, so the agent must infer which person-related list it needs.

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?

The description only implies its use case through the word 'ativas'; there is no explicit when-to-use, when-not-to-use, or named alternative among the many person-related siblings. An agent reading only this text would not know whether invitations or settlements require a different tool.

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