Onça Setorial

Regulatory acts and deadlines for a sector

regulatory_events

Read-onlyIdempotent

For one of your licensed sectors: public consultations and other regulatory deadlines falling due in the next days, then the acts published in the current window (Diário Oficial, the sector regulator, Câmara/Senado), each with its lifecycle stage and a link to the act. Use for 'which regulatory deadlines are coming up in energy'. Deterministic: computed from official datasets, no model in the loop.

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": {
      "sector": "<sector>"
    },
    "name": "regulatory_events"
  }
}

Input Schema

Name	Required	Description	Default
`days`	No	Optional. Deadline horizon in days, default 90.
`sector`	Yes	Sector: energy, health, pharmaceutical, telecom, logistics, last_mile, agro, retail, mining or aviation (Portuguese names work too).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds real behavioral context beyond them: the data sources (Diário Oficial, sector regulator, Câmara/Senado), the deterministic computed-from-official-datasets guarantee, and the two-part result ordering (deadlines first, then current acts).

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 dense, front-loaded sentence for the payload plus a short usage cue and a trust signal — no padding or restatement of the title. The middle clause listing sources is a long parenthetical, but every element carries information.

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?

With no output schema, the description does the necessary work of describing the return: past-deadlines list then current acts, each with lifecycle stage and link. Combined with fully documented params and read-only annotations, only minor gaps remain (no pagination/volume indication for a 365-day horizon).

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%, with the sector list, the 1-365 range and the 90-day default all documented in the schema. The description only re-frames `days` as a "deadline horizon" and notes it applies to deadlines rather than acts; it adds little interpretation the schema does not already carry, so baseline 3 is right.

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+resource: returns public consultations/regulatory deadlines due within `days` plus acts published in the current window, for a licensed sector. The scope (one sector, deadline horizon, current acts window) and the payload shape (lifecycle stage + link) are concrete enough that an agent can distinguish it from reconciliation-style siblings like consultation_outcome or rule_enforcement.

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?

Gives an explicit trigger phrase — "Use for 'which regulatory deadlines are coming up in energy'" — and a precondition ("one of your licensed sectors"). It stops short of naming when NOT to use it or pointing at specific alternatives for act-level or enforcement-level questions, so 4 rather than 5.

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

All Onça Setorial tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?