Skip to main content
Glama

juba_advanced_search

Search legal rulings from Buenos Aires courts with field-specific filters for summary text, case details, cited norms, and ruling types using structured queries.

Instructions

Advanced search on JUBA with field-specific filtering.

Searches across specific fields like summary text, voces (legal topics),
case caption (caratula), full ruling text, or cited norms.

Args:
    query: Search terms. Supports etiquetas like "Caratula:Garcia" or "TipoFallo:S".
    fields: Which fields to search in. Default: ["texto_sumario"].
            Options: materia, voces, nro_causa, caratula, texto_sumario,
            juez_voto, codigo_norma, nro_norma, anio_norma,
            texto_completo, tribunal_emisor.
    tipo_fallo: Filter by ruling type. S=Definitiva, I=Interlocutoria, P=Plenario.
    fecha_desde: Start date filter (DD/MM/YYYY).
    fecha_hasta: End date filter (DD/MM/YYYY).

Returns:
    JSON with total count and result list with same structure as juba_search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
fieldsNo
tipo_falloNo
fecha_desdeNo
fecha_hastaNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses the search behavior, field options, and return format, but doesn't mention rate limits, authentication requirements, pagination behavior, or error conditions. It adequately describes what the tool does but lacks operational details an agent might need for robust invocation.

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 well-structured with clear sections (purpose, args, returns) and uses bullet-like formatting for parameters. Every sentence adds value, though the field options list is quite long. It's appropriately sized for a 5-parameter advanced search tool, though could be slightly more concise in the fields enumeration.

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?

Given 5 parameters with no schema descriptions and an output schema present, the description provides excellent parameter documentation and clarifies the return structure references 'juba_search'. It covers the core functionality well, though additional behavioral context (like rate limits or authentication) would make it more complete for a search tool with no annotations.

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?

With 0% schema description coverage, the description fully compensates by providing detailed parameter semantics: it explains query supports specific etiquetas syntax, lists all field options with their meanings, decodes tipo_fallo values (S=Definitiva, etc.), and specifies date format (DD/MM/YYYY). This adds substantial value beyond the bare schema.

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 performs 'Advanced search on JUBA with field-specific filtering' and specifies it searches across specific fields like summary text, legal topics, case caption, etc. It distinguishes from sibling 'juba_search' by emphasizing field-specific filtering and advanced capabilities, providing clear differentiation.

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 implies usage context by mentioning 'advanced search' and listing specific searchable fields, suggesting this is for more targeted queries than basic search. However, it doesn't explicitly state when to use this versus 'juba_search' or 'juba_get_fallo', nor does it provide exclusion criteria or prerequisites for usage.

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

Install Server

Other Tools

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/frontalinilucas/juba-mcp'

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