Convoca

Libros premiados

libros_premiados

Read-onlyIdempotent

Libros publicados que han ganado un premio literario, del más reciente al más antiguo, con editorial, ISBN, fecha y su ficha en Convoca. Filtra por texto (título, autoría o premio), lengua del libro y 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": "libros_premiados"
  }
}

Input Schema

Name	Required	Description
`texto`	No	Palabras del título del libro, de la obra premiada, de quien la escribió o del nombre del premio.
`cursor`	No	El «siguiente» de la respuesta anterior, para seguir por donde iba, con los mismos filtros.
`lengua`	No	Lengua del libro, en palabras: «catalán», «castellano», «gallego»…
`limite`	No	Cuántos devolver como mucho (20 si no se dice).
`desde_anyo`	No	Solo premios de ese año en adelante.

Output Schema

Name	Required	Description
`total`	Yes	Cuántos casan con la búsqueda, en todas las páginas.
`libros`	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.

Changed1 schema field changedOct 29, 2026

addedInput schema / properties / texto / description

Added value: +"Palabras del título del libro, de la obra premiada, de quien la escribió o del nombre del premio."

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": {
+    "datos_de": {
+      "description": "Cuándo se generaron los datos (ISO 8601): la instantánea.",
+      "type": "string"
+    },
+    "devueltos": {
+      "type": "integer"
+    },
+    "libros": {
+      "items": {
+        "properties": {
+          "anyo": {
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "autor": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "editorial": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "ficha": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "isbn": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "lengua": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "pagina_premio": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "premio": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "publicado": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "titulo": {
+            "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",
+    "libros",
+    "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 readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description still earns credit for adding real operational context the annotations cannot: the result ordering (newest first) and the shape of each record (publisher, ISBN, date, Convoca link). Pagination is left to the schema's cursor field, which is a minor omission.

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?

Two sentences, front-loaded with what the resource is and what gets returned, then filters. Nothing is redundant. Slightly dense packing of field lists, but every clause carries information.

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?

With an output schema present, return values need no explanation, and annotations carry the safety profile; the description fills in ordering and record contents, which is what an agent needs to choose this over siblings. The only real gap is the missing explicit contrast with buscar_premios/palmares.

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%, so the baseline is 3. The description restates the filter axes — text over title/authorship/prize, language, year — matching the schema's own text without adding format, matching rules, or anything about how texto interacts with lengua/desde_anyo or how cursor must be reused.

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?

States a specific resource and scope: "Libros publicados que han ganado un premio literario", with the ordering made explicit ("del más reciente al más antiguo"). It also names the returned fields, so an agent knows this is a book-level list rather than a prize-level one. It stops short of naming the sibling it is not (e.g. buscar_premios or palmares), which keeps it at 4.

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 filter dimensions ("Filtra por texto… lengua… y año") imply the retrieval scenarios, so usage is inferable. But there is no explicit when-to-use, no exclusion, and no routing to the obviously adjacent siblings buscar_premios or palmares, which is the main ambiguity risk here.

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?