Convoca

Buscar premios

buscar_premios

Read-onlyIdempotent

Encuentra premios literarios por nombre, quien convoca, género o lengua, tengan o no la convocatoria abierta. Devuelve su identificador (slug) para ver_premio.

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

Input Schema

Name	Required	Description
`texto`	No	Palabras del nombre o de quien convoca.
`cursor`	No	El «siguiente» de la respuesta anterior, para seguir por donde iba, con los mismos filtros.
`genero`	No	Género del premio, con los valores de buscar_convocatorias: cuento es relato y microrrelato; teatro incluye guion; ensayo incluye investigación; periodismo, artículos.
`lengua`	No	Lengua en la que se escriben las obras del premio.
`limite`	No	Cuántos devolver como mucho (15 si no se dice).
`solo_abiertos`	No	Solo los que tienen la convocatoria abierta.

Output Schema

Name	Required	Description
`total`	Yes	Cuántos casan con la búsqueda, en todas las páginas.
`ultima`	No	Posición del último de esta página.
`premios`	Yes
`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.

Changed2 schema fields changedNov 1, 2026

changedInput schema / properties / genero / description

Previous value: -"Género del premio, con los valores de buscar_convocatorias: cuento es relato y microrrelato; teatro incluye guion; traduccion_ensayo, ensayo y traducción."New value: +"Género del premio, con los valores de buscar_convocatorias: cuento es relato y microrrelato; teatro incluye guion; ensayo incluye investigación; periodismo, artículos."

changedInput schema / properties / genero / enum

Previous value: -[
-  "poesia",
-  "novela",
-  "cuento",
-  "teatro",
-  "comic",
-  "traduccion_ensayo",
-  "no_ficcion",
-  "obra_publicada",
-  "otro"
-]New value: +[
+  "poesia",
+  "novela",
+  "cuento",
+  "teatro",
+  "comic",
+  "ensayo",
+  "periodismo",
+  "traduccion",
+  "no_ficcion",
+  "obra_publicada",
+  "otro"
+]

Changed2 schema fields changedOct 29, 2026

addedInput schema / properties / genero / description

Added value: +"Género del premio, con los valores de buscar_convocatorias: cuento es relato y microrrelato; teatro incluye guion; traduccion_ensayo, ensayo y traducción."

addedInput schema / properties / lengua / description

Added value: +"Lengua en la que se escriben las obras del premio."

Changed1 schema field changedOct 28, 2026

changedInput schema / properties / genero / enum

Previous value: -[
-  "poesia",
-  "novela",
-  "cuento",
-  "teatro",
-  "comic",
-  "infantil_juvenil",
-  "traduccion_ensayo",
-  "no_ficcion",
-  "obra_publicada",
-  "otro"
-]New value: +[
+  "poesia",
+  "novela",
+  "cuento",
+  "teatro",
+  "comic",
+  "traduccion_ensayo",
+  "no_ficcion",
+  "obra_publicada",
+  "otro"
+]

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"
+    },
+    "premios": {
+      "items": {
+        "properties": {
+          "abierta": {
+            "type": [
+              "boolean",
+              "null"
+            ]
+          },
+          "cierre": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "entidad": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "fallos": {
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "generos": {
+            "type": [
+              "array",
+              "null"
+            ]
+          },
+          "lenguas": {
+            "type": [
+              "array",
+              "null"
+            ]
+          },
+          "libros": {
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "nombre": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "pagina": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "slug": {
+            "type": "string"
+          },
+          "ultimo_cierre": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "slug"
+        ],
+        "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",
+    "premios",
+    "siguiente"
+  ],
+  "type": "object"
+}

First observedOct 22, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds useful behavior beyond them: results include both open and closed calls, and each hit carries a slug identifier for the detail tool. Pagination behavior is left to the cursor param rather than described.

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

Conciseness5/5

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

Two sentences, no filler. Scope and return value are front-loaded in the first sentence, and the follow-up pointer closes it.

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?

With rich annotations, a fully described 6-parameter schema (all optional) and an output schema, the description supplies everything still needed: it is a read-only, idempotent search over open and closed awards whose output feeds ver_premio. Nothing material is missing.

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%, including enum value explanations for genero and lengua, so the parameters are already fully documented. The description only restates the filter concepts at a high level and adds no syntax, matching or ranking details. 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?

States a concrete verb and resource ("Encuentra premios literarios") and enumerates the filterable dimensions (nombre, quien convoca, género, lengua), plus what comes back ("su identificador (slug)"). It implicitly separates itself from buscar_convocatorias by covering awards "tengan o no la convocatoria abierta", but never names that sibling explicitly.

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?

Clarifies the scope condition — the search spans open and closed calls — and points to the follow-up step ("para ver_premio"), which gives an agent a clear workflow. It stops short of stating when to prefer buscar_convocatorias or libros_premiados instead.

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?