Convoca

Palmarés

palmares

Read-onlyIdempotent

Quién ganó los premios literarios que sigue Convoca: año, obra, autoría y libro publicado, con la fuente donde se anunció el fallo. Solo fallos validados a mano o con dos fuentes. Filtra por premio, autoría, obra o año.

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

Input Schema

Name	Required	Description
`anyo`	No	Año del premio.
`obra`	No	Título de la obra premiada o de su libro, entero o en parte; no cuentan los acentos ni las mayúsculas.
`autor`	No	Nombre de quien ganó, entero o en parte; no cuentan los acentos ni las mayúsculas.
`cursor`	No	El «siguiente» de la respuesta anterior, para seguir por donde iba, con los mismos filtros.
`limite`	No	Cuántos fallos devolver como mucho (20 si no se dice).
`premio`	No	Nombre o slug del premio.

Output Schema

Name	Required	Description
`aviso`	No
`total`	Yes	Cuántos casan con la búsqueda, en todas las páginas.
`fallos`	Yes
`ultima`	No	Posición del último de esta página.
`primera`	No	Posición del primero de esta página, desde 1.
`datos_de`	Yes	Cuándo se generaron los datos (ISO 8601): la instantánea.
`devueltos`	Yes
`siguiente`	Yes	Cursor de la página siguiente: pásalo en «cursor». null si no hay más.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 29, 2026

addedInput schema / properties / anyo / description
```
Added value: +"Año del premio."
```

addedInput schema / properties / autor / description

Added value: +"Nombre de quien ganó, entero o en parte; no cuentan los acentos ni las mayúsculas."

addedInput schema / properties / obra / description

Added value: +"Título de la obra premiada o de su libro, entero o en parte; no cuentan los acentos ni las mayúsculas."

Changed2 schema fields changedOct 26, 2026

addedInput schema / properties / cursor

Added value: +{
+  "description": "El «siguiente» de la respuesta anterior, para seguir por donde iba, con los mismos filtros.",
+  "maxLength": 300,
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "aviso": {
+      "type": "string"
+    },
+    "datos_de": {
+      "description": "Cuándo se generaron los datos (ISO 8601): la instantánea.",
+      "type": "string"
+    },
+    "devueltos": {
+      "type": "integer"
+    },
+    "fallos": {
+      "items": {
+        "properties": {
+          "anyo": {
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "autor": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "fuentes": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "libro": {
+            "properties": {
+              "editorial": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "ficha": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "isbn": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "lengua": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "publicado": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "titulo": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "obra": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "pagina_premio": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "premio": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "primera": {
+      "description": "Posición del primero de esta página, desde 1.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "siguiente": {
+      "description": "Cursor de la página siguiente: pásalo en «cursor». null si no hay más.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "total": {
+      "description": "Cuántos casan con la búsqueda, en todas las páginas.",
+      "type": "integer"
+    },
+    "ultima": {
+      "description": "Posición del último de esta página.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "datos_de",
+    "total",
+    "devueltos",
+    "fallos",
+    "siguiente"
+  ],
+  "type": "object"
+}

First observedOct 22, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely useful behavioural context beyond that: results are restricted to hand-validated verdicts or those backed by two sources, and each record carries the source where the ruling was announced — an agent knows to expect curated but possibly incomplete coverage.

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?

Three tight sentences: what it returns first, the data-quality guarantee second, the filter surface last. No filler, though the filter sentence largely duplicates information an agent will read in the schema.

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?

An output schema exists, so return fields (including the fuente) need not be spelled out, and annotations cover the safety profile. The description closes the remaining gaps that matter — provenance and validation policy — leaving only the sibling routing and pagination semantics unaddressed.

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?

Schema description coverage is 100%, with accent/case-insensitivity, max lengths and the cursor contract all documented in the schema itself, so the baseline is 3. The description's 'Filtra por premio, autoría, obra o año' restates the same dimensions without adding syntax, matching rules or pagination hints beyond what the schema supplies.

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?

The description states a concrete resource — who won the literary awards Convoca tracks — and enumerates the returned fields (año, obra, autoría, libro publicado, fuente), which tells an agent exactly what this tool yields. It is clearly not a search of award definitions or a book catalogue, but it never names a sibling (buscar_premios, libros_premiados) to make the boundary explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The closing sentence 'Filtra por premio, autoría, obra o año' implies how to use it, and the two-source/sourced-verdict rule hints at the scope of what is returned. There is no explicit when-to-use versus when-not-to-use guidance and no reference to the sibling tools an agent must choose between.

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

All Convoca 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?