Skip to main content
Glama

Astrea (Aurum)

by io.github.mcp-dir
OverviewDiscussionsAdmin

astrea_andamento_criar

Lança um andamento (histórico) MANUAL num processo do Astrea — registra um ato/observação na timeline do processo (não é captura automática do tribunal).

  • case_id: id do processo (ver astrea_processos).

  • description: texto do andamento (aceita HTML simples; texto puro vira um parágrafo).

  • date: data/hora do andamento em ISO (ex.: 2026-06-30 ou 2026-06-30T13:00:00Z); omita para usar agora.

  • responsible_id: opcional, id do membro que PRATICOU o ato (ver astrea_responsaveis). Se omitir, o andamento fica assinado pelo usuário da integração, não pelo advogado — passe o id da pessoa para a timeline mostrar quem de fato praticou.

Bulk support: accepts case_ids, responsible_ids for batched execution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNo
case_idYes
case_idsNo
descriptionYes
responsible_idNo
responsible_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / responsible_id
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / responsible_ids
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations indicate a write operation, but the description adds crucial behavioral detail: omitting responsible_id causes the entry to be attributed to the integration user rather than the lawyer, and bulk execution is explicitly disclosed. This goes well beyond the structured annotations and helps the agent predict side effects.

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?

The description front-loads the core purpose, then uses compact parameter-by-parameter lines with defaults and caveats, and closes with a one-line bulk note. Every sentence adds value and the structure is easy to scan.

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?

The description is highly complete for a create operation, but there is minor ambiguity around bulk usage: the schema lists case_id as required while the description says case_ids is accepted for batched execution, without clarifying whether singular fields should be omitted in bulk mode. Return/error behavior is also not mentioned, though the tool has no output schema.

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 description coverage is 0%, but the description compensates fully by explaining case_id, description, date format and default behavior, responsible_id semantics, and the bulk parameters case_ids and responsible_ids. The agent gets actionable meaning beyond raw schema types.

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?

The description opens with a specific verb-resource pair: 'Lança um andamento (histórico) MANUAL num processo do Astrea — registra um ato/observação na timeline'. It also explicitly contrasts this with automatic court capture, which distinguishes it from other Astrea tools and clarifies what kind of operation this is.

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?

The description clearly frames this as the manual timeline-entry tool and notes it is not automatic tribunal capture, giving the agent a decision criterion. It also points to astrea_processos and astrea_responsaveis for ID lookups. However, it does not explicitly mention when to prefer sibling tools like astrea_andamentos for reading timeline data.

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