Clerk - IA Legal Dominicana

Explorar valores de un filtro

explorar_facetas

Read-only

Publica el vocabulario REAL de un filtro, con el número de documentos de cada valor. Un valor con conteo es un valor que funciona como filtro, y esta es la única fuente fiable de esos valores.

Con contiene se busca dentro de la faceta. Si no aparece, la respuesta dice que ese valor no existe con esa grafía y ofrece las parecidas, en lugar de dejar que se filtre por él y devuelva un cero que aparenta ser un hecho del mundo.

Con terminos o tribunal los conteos son los de ESA búsqueda, que es como se ve qué salas o materias tienen algo del tema antes de gastar una consulta.

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": {
      "faceta": "<faceta>"
    },
    "name": "explorar_facetas"
  }
}

Input Schema

Name	Required	Description
`tope`	No	Cuántos valores devolver.
`faceta`	Yes	Qué filtro explorar. Acepta tanto el nombre que usa buscar_jurisprudencia (sala, materia, via) como el interno (instancia, ambitos, tipoproceso).
`contiene`	No	Filtra los valores que contengan este texto (sin tildes ni mayúsculas).
`terminos`	No	Acota los conteos a esta búsqueda.
`tribunal`	No	Acota los conteos a estos tribunales.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 18, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations only say readOnly and openWorld, so the description usefully adds that the counts are the authoritative source of valid filter values and that an unmatched `contiene` returns a "does not exist with that spelling" answer plus near matches instead of a misleading zero. That is real behavioral disclosure beyond the structured fields; only ordering/pagination of the result list is left unspecified.

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?

Core purpose is front-loaded in the first sentence, then parameters are addressed in short, scoped paragraphs. Slightly verbose in the middle paragraph, but each sentence carries information the agent needs.

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?

For a 5-parameter read-only tool with no output schema, the description conveys enough about the return: values paired with document counts and a spelling-suggestion path on misses. Missing only secondary details such as result ordering or how many values come back by default beyond the schema's `tope`.

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?

With 100% schema coverage the baseline is 3, and the description earns above it by explaining the semantics of `contiene` (in-facet search with fuzzy fallback) and clarifying that `terminos` and `tribunal` scope the counts to that particular search rather than global counts. `tope` and the enum aliases are left to the schema, which already documents them well.

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?

"Publica el vocabulario REAL de un filtro, con el número de documentos de cada valor" gives a specific verb (publica) plus resource (valores de un filtro) and states the shape of the output. It is unmistakably a facet/vocabulary introspection tool rather than a search, though it never names a sibling to contrast with.

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 last clause establishes context for use: checking which salas or materias have material "antes de gastar una consulta", which tells the agent this is a cheap pre-flight step before a real search. It stops short of naming the search tool to use afterwards or any explicit when-not-to-use case.

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

All Clerk - IA Legal Dominicana tools Inspect

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

Need Help?