Skip to main content
Glama

Archivo de Esto También es Política

Ver un episodio

ver_episodio
Read-onlyIdempotent

Devuelve el resumen, los puntos clave, los capítulos con su segundo y el enlace de un episodio de «Esto También es Política».

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": {
      "episodio": "<episodio>"
    },
    "name": "ver_episodio"
  }
}

Input Schema

NameRequiredDescriptionDefault
episodioYesClave del episodio, tal como aparece en el campo «episodio» de los resultados, por ejemplo «episode-207» o «capsula-3».

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / episodio / description
      Previous value: -"Clave del episodio, por ejemplo «episode-207» o «capsula-3»."New value: +"Clave del episodio, tal como aparece en el campo «episodio» de los resultados, por ejemplo «episode-207» o «capsula-3»."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds value by specifying exactly what payload comes back (summary, key points, chapters with timestamps, link), though it says nothing about behavior for an invalid or unknown key.

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?

A single sentence that front-loads the verb and packs the return contents without filler. Nothing is redundant or misplaced.

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?

For a one-parameter read tool with a fully documented schema and no output schema, the description compensates by enumerating the returned fields. Only the failure mode for an unknown key is left unstated, a minor gap given the annotations.

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% and the episodio property already documents the key format with concrete examples like «episode-207» and «capsula-3». The description adds no further meaning about the parameter, so the baseline 3 applies.

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 verb (devuelve) and resource (un episodio de «Esto También es Política») and enumerates the returned elements: resumen, puntos clave, capítulos con su segundo y enlace. This makes it easy to separate from search-style siblings like buscar_episodios, though no sibling is named explicitly.

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: fetch one episode by its key. The description never says when to prefer this over buscar_episodios or leer_fragmento, nor that it requires a key obtained from a prior search, so the agent must infer the workflow.

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