Skip to main content
Glama

Procesos Consultar Radicado

procesos_consultar_radicado
Read-onlyIdempotent

Query a Colombian judicial case by its 23-digit radicado through public court records, with an option to return only active processes.

Instructions

Consulta un proceso judicial por radicado de 23 dígitos (consulta pública; API interna del portal).

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": {
      "radicado": "<radicado>"
    },
    "name": "procesos_consultar_radicado"
  }
}

Input Schema

NameRequiredDescriptionDefault
radicadoYes
solo_activosNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds a meaningful behavioral note that results come from an internal portal API (suggesting possible availability or scraping fragility), but says nothing about behavior on invalid or malformed radicados or on not-found cases.

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?

A single compact sentence that front-loads the resource and the key constraint (23 digits). Nothing is wasted, though the brevity contributes to the uncovered 'solo_activos' parameter.

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

Completeness3/5

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

An output schema exists, so return-value documentation is not required. For a two-parameter lookup tool the remaining gap is the unexplained 'solo_activos' filter and the lack of any note on error or empty-result behavior, making it adequate but incomplete.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the burden for both parameters. It explains the required 'radicado' as a 23-digit case identifier, but 'solo_activos' (boolean, default false) is left completely undefined in both schema and description, and the radicado format is not illustrated.

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

Purpose4/5

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

The description names a specific verb (consulta) and resource (proceso judicial) plus the lookup key (radicado de 23 dígitos), which is enough to distinguish it from a sibling like procesos_actuaciones. It stops short of explicitly contrasting itself with any sibling, so it is clear but not fully differentiated.

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

Usage Guidelines3/5

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

'Consulta pública' implies the read-only lookup use case and signals the operation is public-facing, but there is no explicit when-to-use or when-not-to-use guidance relative to the listed alternatives. The agent must infer that this tool is for fetching a single case by radicado rather than for listing actuaciones.

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