Skip to main content
Glama
Sign In
normas-psav

normas-psav

by BrunooMoniz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

norma

Retrieve a Brazilian BCB, CMN, or CVM virtual-asset regulation by name or ID to view its summary, current status, amendments, revocations, citations, and optional article text.

Instructions

Mostra uma norma: ementa, situação de vigência, quem a alterou ou revogou, o que ela altera, revoga e cita.

identificacao: o nome ("Resolução BCB 520", "Parecer de Orientação CVM 40") ou o id que buscar devolve. artigo: opcional; com "4" ou "Art. 4º" devolve o texto desse artigo (em norma com anexos, de todos os que tiverem esse número).

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": {
      "identificacao": "<identificacao>"
    },
    "name": "norma"
  }
}

Input Schema

NameRequiredDescriptionDefault
artigoNo
identificacaoYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the return content (summary, validity status, alteration/revocation relationships, citations) and an edge-case behavior for the `artigo` parameter in norms with annexes. It does not mention read-only semantics explicitly, though "Mostra" implies retrieval.

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?

Front-loaded with what the tool returns, then per-parameter notes, with no filler. The parenthetical about annexes is slightly dense but earns its place by preventing wrong expectations.

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 two-parameter read tool with an output schema, the definition covers input formats, optionality, and the main behavioral edge case. Only minor gaps remain, such as error behavior for an unknown name.

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

Parameters5/5

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

Schema coverage is 0%, so the description must compensate, and it does: `identificacao` accepts a name with realistic examples or an id returned by `buscar`, and `artigo` is optional and accepts both "4" and "Art. 4º" forms. Both parameters gain meaning beyond the bare schema.

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

Purpose5/5

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

Names a specific verb ("Mostra") and resource ("uma norma") and enumerates exactly what is returned: ementa, situação de vigência, quem a alterou ou revogou, o que ela altera, revoga e cita. It also distinguishes itself from the sibling `buscar` by naming it as the source of the `id` value used here.

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

Usage Guidelines4/5

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

Implies the workflow: use `buscar` to obtain the id, then call `norma` with either a human name or that id, and optionally an article. It gives clear context but never states when not to use it or how it differs from `panorama`.

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

Deploy Server

Other Tools