Skip to main content
Glama

Conector Juspronto

Agenda do escritório

agenda
Read-only

A agenda do escritório em uma chamada: prazos em aberto (incluindo atrasados), prazos SUGERIDOS ainda não confirmados (prazosSugeridos), audiências e reuniões dos próximos dias. Use para "o que eu tenho hoje/esta semana?" ou "o que vence?". NÃO use para histórico (ultimas_movimentacoes) nem para um processo específico (listar_prazos com processoId). Até 24 mil caracteres; tetos: 40 prazos, 20 audiências, 20 reuniões. Havendo mais, truncado vem true, totais traz o total de cada lista e o aviso diz qual foi cortada; se nem os prazos vencidos, de hoje e urgentes couberem, proximoCursor continua em listar_prazos (mesmos dias). Descrições cortadas em 280 caracteres (detalhe_processo lê o inteiro). prazosSugeridos: as 20 primeiras a vencer, resumidas (o texto inteiro está em listar_prazos); as já vencidas, em vencidas (as 5 mais recentes). totalSugeridos soma as duas, não a fila inteira (juspronto://prazos-sugeridos). janela: de agora até o fim dos dias pedidos; painel_hoje conta audiências de hoje em diante.

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

Input Schema

NameRequiredDescriptionDefault
diasNoJanela em dias à frente (padrão 7, máximo 31)

Output Schema

NameRequiredDescriptionDefault
avisoNo
prazosNo
totaisNo
mensagemNo
reunioesNo
truncadoNo
vencidasNo
audienciasNo
janelaDiasNo
avisoConteudoNo
proximoCursorNo
avisoSugeridosNo
totalSugeridosNo
prazosSugeridosNo
temMaisSugeridosNo
sugeridosVencidosNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / proximoCursor
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "audiencias": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {},
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "aviso": {
      +      "type": "string"
      +    },
      +    "avisoConteudo": {
      +      "type": "string"
      +    },
      +    "avisoSugeridos": {
      +      "type": "string"
      +    },
      +    "janelaDias": {
      +      "type": "number"
      +    },
      +    "mensagem": {
      +      "type": "string"
      +    },
      +    "prazos": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "cnjFormatado": {
      +            "anyOf": [
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          },
      +          "pasta": {
      +            "anyOf": [
      +              {
      +                "type": "number"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          },
      +          "prazoId": {
      +            "type": "string"
      +          },
      +          "processoId": {
      +            "anyOf": [
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "prazosSugeridos": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {},
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "reunioes": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {},
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "sugeridosVencidos": {
      +      "type": "number"
      +    },
      +    "temMaisSugeridos": {
      +      "type": "boolean"
      +    },
      +    "totais": {
      +      "additionalProperties": {},
      +      "properties": {},
      +      "type": "object"
      +    },
      +    "totalSugeridos": {
      +      "type": "number"
      +    },
      +    "truncado": {
      +      "type": "boolean"
      +    },
      +    "vencidas": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {},
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses concrete operational behavior: the 24k character limit, per-list caps (40 deadlines, 20 hearings, 20 meetings), truncation flags (`truncado`, `totais`, `aviso`), 280-character description clipping, and the `proximoCursor` continuation rule. It also explains how `prazosSugeridos` is summarized, how `vencidas` works, and what `totalSugeridos` sums, which is unusually thorough behavioral context.

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?

The description is front-loaded with purpose, then routing exclusions, then limits and truncation behavior. Every clause carries operational information, but the single dense paragraph with many semicolon-separated caveats is harder to scan than a short bulleted structure would be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's aggregation complexity, an output schema already exists so return values need not be explained. The description still covers the critical edge cases an agent needs: truncation, per-list totals, suggested-deadline summarization, and cursor continuation, leaving no significant gap for correct invocation.

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 100%, so the schema already documents `dias` with its default and maximum. The description adds meaningful semantics by defining the window as 'de agora até o fim dos dias pedidos' and clarifying that `painel_hoje` counts hearings from today onward, which goes beyond the schema's bare range description.

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 states a specific aggregation purpose: open deadlines (including overdue), unconfirmed suggested deadlines, hearings, and meetings for upcoming days. It explicitly distinguishes itself from `ultimas_movimentacoes` for history and from `listar_prazos` with `processoId` for a single case, so an agent can route correctly without opening another schema.

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?

It gives explicit when-to-use examples ('o que eu tenho hoje/esta semana?' / 'o que vence?') and explicit when-not-to-use cases with the alternative tool named for each. It also explains the fallback path via `proximoCursor` in `listar_prazos` when even urgent deadlines do not fit.

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