Skip to main content
Glama
OpenMonetis MCP

OpenMonetis MCP

by Welington98

Convites entre pessoas

list_person_invitations
Read-onlyIdempotent

Lists sent connection invitations and shows each status (pending, claimed, confirmed, cancelled, expired) plus deadlines, helping you track pending or overdue invites.

Instructions

Lista os convites de conexão enviados, com status (pending, claimed, confirmed, cancelled, expired) e prazos.

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_invitations"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this a safe, idempotent, non-destructive read in a closed system. The description adds genuinely useful disclosure about returned content — the five status values and the presence of deadlines — which is valuable given there is no output schema. It says nothing about ordering, pagination, or whether received invitations are excluded.

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?

A single front-loaded sentence with no filler; the resource is stated first and qualifying detail follows. It is efficient, though slightly terse for a tool whose return shape has to be inferred from prose.

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?

With no output schema and no parameters, the description carries the burden of explaining return content, and it partially does so via the status enum and deadlines. Gaps remain around result ordering, volume/pagination, and whether the list covers invitations sent by the current user only.

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?

Zero parameters, and the schema coverage is 100%, so no parameter meaning is required from the description. The description correctly stays silent on inputs rather than inventing any.

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?

Names a concrete verb and resource ('Lista os convites de conexão enviados') and narrows scope to sent invitations, listing the statuses involved. It never names a sibling such as list_person_connections or cancel_person_invitation, so differentiation is left to the reader.

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 explicit when-to-use or when-not-to-use guidance and no pointer to alternatives for related reads (e.g. listing confirmed connections) or lifecycle actions (cancel/revoke/create). The word 'enviados' implies scope but does not guide tool selection.

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