Skip to main content
Glama

Es la hora de la verdad (Congreso de los Diputados)

Elecciones generales del 29 de noviembre

ver_elecciones_29n
Read-onlyIdempotent

Elecciones generales del 29 de noviembre de 2026: qué se elige, el calendario oficial con el estado de cada plazo hoy (voto por correo, censo, campaña, jornada de reflexión…) y su fuente y, si se indica una provincia, cuántos diputados y senadores le corresponden y sus candidaturas cuando las publique el BOE (las presentadas, provisionales y marcadas como tales, hasta que se publiquen las proclamadas). Incluye la guía práctica de la web, el estado de los programas electorales y el test «¿Con quién coincides?», que compara las respuestas de cada persona con lo que votó cada grupo en el Congreso (no es una recomendación de voto). Cada respuesta incluye «url», la página de la web que respalda los datos, y su «atribucion»: la licencia CC BY 4.0 exige citar la fuente y enlazar esa página.

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

Input Schema

NameRequiredDescriptionDefault
provinciaNoProvincia o ciudad autónoma (opcional), p. ej. «Huesca».

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (already covering read-only/idempotent/non-destructive), the description discloses real behavioral traits: candidacies are provisional and flagged as such until the BOE publishes the proclaimed lists, every answer carries a «url» and an «atribucion» because CC BY 4.0 obliges citation, and the test is explicitly not a voting recommendation. These are useful data-freshness, provenance and legal-use disclosures that the annotations cannot convey.

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 subject is front-loaded correctly, but the body is one sprawling sentence that strings together a dozen unrelated features before reaching the second sentence on url/atribucion. The density makes it hard to scan; the same content could be split into short labeled sentences without losing anything.

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 no output schema, the description carries the burden of describing returns and does so: it names the calendar status, provincial seats and candidacies, and the per-answer «url» and «atribucion» fields. Nothing essential for a correct informational call is missing, though the absence of any note on how current the calendario data is leaves a small gap.

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 single optional parameter is documented there, so the baseline would be 3. The description nonetheless adds genuine meaning by stating the consequence of supplying provincia — seat counts for deputies and senators plus its candidacies — which the schema's 'p. ej. «Huesca»' does not explain.

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 resource (las elecciones generales del 29N de 2026) and enumerates exactly what it returns: calendario con estado de cada plazo, diputados/senadores por provincia, candidaturas del BOE, guía práctica, estado de programas y el test «¿Con quién coincides?». An agent can tell what it does without the schema, but the description never names siblings (ver_programas_29n, ver_provincia, buscar_diputados) whose territory it partially overlaps, so differentiation is only implicit.

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?

Usage is only implied: it explains that passing a provincia adds seat counts and candidacies, which tells the agent how to shape a call but not when to prefer this tool over ver_programas_29n or ver_provincia. There are no explicit 'use this when / use X instead' statements despite obvious overlap with the sibling tools.

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