Skip to main content
Glama

Listar los tribunales de una corte y su código

listar_tribunales
Read-onlyIdempotent

Get the tribunal codes required for first-instance case searches. Enter a court code to retrieve its tribunals, enabling case lookup and following exhortos.

Instructions

Los tribunales de una corte, con el código que las búsquedas exigen.

Llamar esto ANTES de buscar en primera instancia: tribunal es obligatorio ahí y su valor no aparece en ninguna otra respuesta, así que sin esto hay que sabérselo de memoria.

También es la forma de seguir un exhorto. El detalle entrega el tribunal de destino por su NOMBRE, y la búsqueda pide el código: se ubica la corte con listar_cortes, se piden sus tribunales acá, y con ese código se busca la causa de destino por su rol.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
corteYesCódigo de la corte, el que entrega `listar_cortes`. Obligatorio: sin él habría que elegir una, y devolver los tribunales de otra jurisdicción es una lista plausible y equivocada.
competenciaNoUna de: civil, cobranza, laboral, penal. Son las que se acotan por tribunal, o sea aquellas donde este listado sirve para buscar. Suprema no tiene tribunales debajo y apelaciones se acota por corte.civil

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changedv0.19.3
    • removedOutput schema / $defs / Tribunal / description
      Removed value: -"Un tribunal de primera instancia, con el código que las búsquedas exigen."
    • removedOutput schema / $defs / Tribunal / properties / codigo / description
      Removed value: -"Lo que va en el parámetro `tribunal` de las búsquedas."
    • removedOutput schema / $defs / Tribunal / properties / nombre / description
      Removed value: -"Nombre tal como lo publica la plataforma."
  2. Addedv0.8.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior, so the description's job is lighter. It adds valuable context: that the tribunal code is not available elsewhere, and that for exhortos the name must be mapped to a code via this tool. No contradictions with annotations.

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 is concise and front-loaded: the first sentence states the purpose, and the following paragraphs give essential usage context without fluff. Every sentence adds value, and the structure aids comprehension.

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?

The description is complete for a listing tool. It explains why the tool is needed, when to use it, how it connects to sibling tools, and what data it returns (codes for searches). The presence of an output schema covers the return structure, so nothing essential is missing.

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?

The schema descriptions for both parameters are already very detailed (100% coverage), explaining the meaning of `corte` and `competencia` and their constraints. The description does not add further parameter semantics beyond what is in the schema, so a baseline score of 3 is appropriate.

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 clearly states the tool's purpose: it lists the tribunals of a court along with the codes that searches require. The title reinforces this with the verb 'Listar'. It also differentiates from siblings by explaining its role as a prerequisite for first-instance searches and for following exhortos, making it distinct from direct search tools.

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?

The description explicitly instructs when to call this tool: 'Llamar esto ANTES de buscar en primera instancia' and 'También es la forma de seguir un exhorto'. It also explains the workflow involving `listar_cortes` and how the returned code is used in a subsequent search, giving clear contextual alternatives.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/notluquis/mcp-pjud-cl'

If you have feedback or need assistance with the MCP directory API, please join our Discord server