Skip to main content
Glama

Próceres · escritos judiciales de España: papeleta, demanda y recursos

Formas jurídicas, campos, decisiones y modalidades de los estatutos

catalogo_formas_estatutos
Read-only

Sin argumentos devuelve el índice de las formas jurídicas que compone componer_estatutos: su identificador, su familia, su norma, su registro, el capital mínimo y cuántos campos, decisiones y modalidades admite. Con forma devuelve la ficha entera de esa forma —cada campo con sus opciones, cada decisión con lo que hace y cada modalidad con su precepto—, que es lo que hay que leer para rellenar datos, decisiones y especialidades sin inventar un valor. Se publica en dos pasos porque la lista de actividades del objeto social tiene cientos de valores y volcarla entera en cada llamada gasta el contexto del modelo sin que lo use. No pide ni devuelve datos personales: el nombre, el DNI, el domicilio y el contacto NO están entre sus campos (el escrito los deja como huecos entre corchetes para que los rellene quien lo presenta). No le pidas esos datos y no los escribas en la llamada.

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

Input Schema

NameRequiredDescriptionDefault
formaNoLa forma de la que se quiere la ficha entera; sin ella, el índice de todas.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only/non-destructive/non-open-world, but the description adds substantial behavior the agent could not infer: the two-step publication is a deliberate context-budget design because the activity list has hundreds of values, and it declares a hard privacy boundary (no name, DNI, domicilio, contacto; documents leave bracketed placeholders). It also discloses the shape of both return modes.

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?

Front-loaded with the two operating modes and their rationale, and every sentence is substantive. The privacy point is restated three times in the closing sentences (no personal data / documents leave brackets / don't request or write it), which costs a little length without new information.

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?

For a single-optional-parameter, fully documented read tool with no output schema, the description is complete: it explains both return modes, why the split exists, and the privacy constraint on inputs. Nothing an agent needs in order to call it correctly is absent.

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% and the enum is documented, so the schema carries the syntax; the description still adds semantic value by contrasting the no-argument vs. `forma` modes and by explaining that the returned record contains each field with its options, each decision with its effect, and each modality with its precepto. This goes beyond the schema's one-line enum note.

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?

States a precise verb and resource: without arguments it returns the index of legal forms that `componer_estatutos` is built from, and with `forma` it returns that form's full record. It explicitly enumerates what the index contains (identifier, family, norma, registro, minimum capital, counts) and what the full record contains, which is enough to tell it apart from the sibling document-composition tools.

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?

It clearly routes usage: call it without `forma` for the index, with `forma` for the full record, and it names `componer_estatutos` as the consumer of this data ("es lo que hay que leer para rellenar `datos`, `decisiones` y `especialidades` sin inventar un valor"). What is missing is an explicit 'do not call this to generate the document' exclusion, though it is strongly implied.

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