Skip to main content
Glama

Listar notas

listar_notas
Read-onlyIdempotent

Histórico de notas da conta, com filtros opcionais.

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": "listar_notas"
  }
}

Input Schema

NameRequiredDescriptionDefault
limiteNoMáx. de notas (1–100, padrão 20).
statusNoFiltro por status.
competenciaNoFiltro YYYY-MM.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds only the account-wide historical scope; it says nothing about ordering, pagination beyond the limite cap, or the shape of 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?

A single short sentence with the scope front-loaded and no filler. It is efficient, though its brevity comes partly from omitting useful information rather than from tight editing.

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 three optional, fully documented parameters and no output schema, most of the agent's needs are met by the structured fields. Still missing is any note on result ordering, the default time window for a 'histórico', or how this relates to consultar_nota — details that matter for a listing tool with no return-value documentation.

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 100% — limite range/default, status enum values, and the competencia YYYY-MM format are all documented in the schema. The description's 'filtros opcionais' merely restates that parameters exist, so the baseline 3 applies.

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

Purpose3/5

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

The description identifies the resource ('notas da conta') and implies a list/history operation via 'Histórico', so the basic purpose is graspable. But it does not state a concrete verb nor distinguish this listing tool from siblings like consultar_nota (single-note lookup) or listar_tomadores, leaving the agent to infer the difference.

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?

'com filtros opcionais' hints that filtering is available but gives no when-to-use guidance, no exclusions, and no pointer to alternatives. An agent gets no help deciding between listar_notas and consultar_nota when looking up a specific note.

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.

Resources