Skip to main content
Glama
Sign In

Astrea (Aurum)

by io.github.mcp-dir
OverviewDiscussionsAdmin

astrea_prazo_excluir

EXCLUI um PRAZO processual do Astrea de vez (ex.: prazo lançado em duplicidade ou por engano). O Astrea NÃO guarda motivo na exclusão e apaga junto as TAREFAS vinculadas. Para registrar o motivo e manter o histórico use astrea_prazo_cancelar; para corrigir data ou dados use astrea_prazo_editar.

  • prazo_id: id do prazo (de astrea_prazo_criar ou de um DEADLINE em astrea_agenda).

Bulk support: accepts prazo_ids for batched execution.

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": {
      "prazo_id": "<prazo_id>"
    },
    "name": "astrea_prazo_excluir"
  }
}

Input Schema

NameRequiredDescriptionDefault
prazo_idYes
prazo_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior1/5

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

The description declares irreversible, cascading deletion ("apaga junto as TAREFAS vinculadas", no reason stored), while the annotations declare destructiveHint=false. That is a direct conflict on the destructive axis, the same failure mode as claiming a write under readOnlyHint=true; an agent receiving both signals cannot trust either. The description's content is richer and arguably the correct side of the conflict, but the contradiction itself is what governs this dimension.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the irreversible-deletion impact, then alternatives, then parameter provenance, then bulk support, with no filler. Each sentence adds information an agent needs before calling.

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?

Covers the critical unknowns for a destructive tool: permanence, cascade to linked tasks, absence of a stored reason, and the safer siblings. Minor gaps remain on bulk return behavior (success/failure per id) and on whether any preconditions or permissions apply, but for a two-parameter delete with no output schema this is nearly complete.

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?

Schema coverage is 0%, so the description carries the load and mostly does: it explains that prazo_id comes from astrea_prazo_criar or a DEADLINE in astrea_agenda, and that prazo_ids enables batched execution. It does not resolve the ambiguity the schema creates, namely whether prazo_id may be empty when prazo_ids is supplied.

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?

States a specific verb and resource plus its permanence ("EXCLUI um PRAZO processual do Astrea de vez") and gives the triggering scenario (duplicate or mistaken entry). It explicitly separates itself from astrea_prazo_cancelar and astrea_prazo_editar, so an agent can tell the three apart without opening schemas.

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

Usage Guidelines5/5

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

Provides explicit routing: use astrea_prazo_cancelar to record a reason and keep history, use astrea_prazo_editar to fix date or data, and use this only for genuinely erroneous/duplicate entries. Both the when and the when-not are stated with the named alternatives.

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

All Astrea (Aurum) toolsInspect
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