Skip to main content
Glama
OpenMonetis MCP

OpenMonetis MCP

by Welington98

Listar pessoas

list_people
Read-onlyIdempotent

Retrieves the installation's people, including administrators and external contacts, with role, status, and relationship so you can obtain IDs for allocations and filters.

Instructions

Lista as pessoas da instalação (administrador e pessoas externas) com papel, status e vínculo. Use os IDs em rateios e filtros.

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

Input Schema

NameRequiredDescriptionDefault
detailNocompact retorna id e nome; full devolve o objeto completo.compact

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 readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds that results carry papel, status and vínculo, which is real value since there is no output schema, but it says nothing about ordering, pagination, or whether all people are returned in one call.

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?

Two compact sentences with the resource and scope front-loaded and the practical hint placed second. Nothing is redundant, though the second sentence is slightly oblique without naming the actual tools involved.

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 read-only list tool with a fully described single parameter, the description covers purpose and the visible fields. It is less complete on return size, ordering, and what "objeto completo" contains for detail=full, which matters because no output schema exists.

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 coverage is 100% and the single "detail" parameter already documents its compact/full enum with defaults. The description adds no extra meaning about when to prefer full over compact, so the baseline of 3 applies.

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?

The description gives a specific verb and resource ("Lista as pessoas da instalação") and narrows the scope to administrator plus external people, plus the attributes returned (papel, status, vínculo). It does not explicitly contrast with nearby siblings such as list_person_connections or list_person_invitations, though the resource noun does most of that work.

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 second sentence tells the agent what the returned IDs are for ("Use os IDs em rateios e filtros"), which is useful downstream context. However, there is no explicit when-to-use versus when-not guidance and no mention of alternatives for narrower person queries.

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