Skip to main content
Glama
Sign In

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

by es.proceres
OverviewDiscussionsAdmin

La vista oral: quién habla y en qué orden, y qué decir en el acto si el juez niega una garantía

hoja_de_sala
Read-only

Devuelve, para una modalidad de vista, el orden de los turnos según la ley y la hoja de fórmulas: lo que se dice en voz alta, sin números de artículo, cuando el juez niega una garantía (la palabra, una prueba, una pregunta, la última palabra…), en el orden en que llega cada momento, y antes lo que no puede faltar: las cargas del acto cuya omisión sanciona la ley sin que el juez haga nada (la falta del abogado a la audiencia previa, el documento de la contraria sin impugnar, la incomparecencia del actor social). Modalidades: social ordinario y despido; civil verbal, audiencia previa y juicio ordinario; contencioso abreviado; penal abreviado y juicio oral ordinario. En lo social es la hoja de quien se defiende solo y admite sus datos (suspensión acordada, abogado pedido sin resolver, recursos pendientes, cifras de la conciliación); fuera de lo social, sinAbogado deja solo lo que la parte puede hacer por sí. Las garantías que se pierden sin protesta son las que, si el abogado calla, mide responsabilidad_letrada (campo vista). 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

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": {
      "modalidad": "<modalidad>"
    },
    "name": "hoja_de_sala"
  }
}

Input Schema

NameRequiredDescriptionDefault
fiscalNoSolo en lo social: si interviene el Ministerio Fiscal (añade su turno).
modalidadYesLa vista: social-ordinario, social-despido, civil-verbal, civil-audiencia-previa, civil-ordinario, contencioso-abreviado, penal-abreviado o penal-ordinario.
pendientesNoSolo en lo social: los recursos o escritos pendientes de resolver, nombrados sin datos personales («mi recurso de reposición de 3 de noviembre»).
sinAbogadoNoFuera de lo social: true si la parte va sin abogado; la hoja deja solo lo que puede hacer por sí.
conciliacionNoSolo en lo social: las cifras de la conciliación, ya calculadas («1.000 €» y «600 €»).
pideCantidadesNoSolo en lo social: la demanda pide una condena en dinero (las conclusiones fijan las cantidades).
sinAbogadoNoLitigaNoSolo en lo social, con abogadoPedidoSinResolver: si se sigue sin abogado, no propone ni practica prueba; mantiene la protesta.
suspensionAcordadaNoSolo en lo social: el juzgado acordó suspender hasta resolver la justicia gratuita y no se ha resuelto.
abogadoPedidoSinResolverNoSolo en lo social: pidió abogado de oficio y no se ha resuelto.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so safety is covered; the description goes beyond by explaining that answers are spoken without article numbers, come in the order the moments occur, and are preceded by the unavoidable burdens. It also discloses a real constraint: no personal data is requested or returned, and the document leaves them as bracketed gaps. Minor gaps remain about output length or format.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core information is front-loaded with "Devuelve", which is good, but it is delivered as one very long run-on sentence that chains modalities, burdens and guaranties together. The personal-data warning is repeated twice ("No pide ni devuelve datos personales... No le pidas esos datos"), costing space. Structuring into separate statements would help considerably.

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?

Though there is no output schema, the description explains what the return looks like (ordered turns, formulas, prior burdens) and pins down the input constraints (no personal data). For a read-only, 9-parameter tool with a required enum, that is largely sufficient. A clearer statement of return shape would close the remaining gap.

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?

With 100% schema description coverage, the schema already explains all nine fields; the description only adds loose context (social vs. non-social behavior, the conciliation figures, the alone-defending party). It does not clarify individual required vs. optional interactions or how `fiscal`, `pendientes` and `conciliacion` alter the returned sheet. Baseline 3 is appropriate.

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?

Opens with a specific verb and resource ("Devuelve, para una modalidad de vista, el orden de los turnos") and states exactly what is produced: the speaking order, the formulas to say aloud when a guarantee is denied, and the prior burdens. It also names the sibling `responsabilidad_letrada` and its `vista` field, so an agent can tell the boundary. The single run-on sentence makes the purpose slower to extract than it needs to be.

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 when-to-use context is explicit: preparing the hearing itself, social cases where the party defends alone and supplies data, and non-social cases where `sinAbogado` trims the sheet. It also routes the related question of lost guarantees to `responsabilidad_letrada`. No parameter-level exclusions or when-not-to-use conditions beyond that are given.

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

All Próceres · escritos judiciales de España: papeleta, demanda y recursos toolsInspect
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