Devuelve la direccion estable para reproducir una emisora en vivo. Usala cuando el usuario quiera escuchar. La direccion es permanente y redirige a la senal vigente; nunca uses la senal de origen directamente porque puede caducar.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Identificador de la emisora, tal como lo devuelve buscar_emisoras. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full transparency burden. It discloses that the returned address is permanent and redirects to the current signal, and warns that the source link may expire. This adds important behavioral context beyond any schema, explaining persistence and redirect behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise and front-loaded with the primary action, then adds a caveat about source expiry. It contains zero fluff and every sentence adds value—coverencing purpose, usage, and a critical warning in two sentences.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has only one parameter and no output schema, and the description covers what it returns, when to use it, and a key caveat. It lacks error handling or return-format details, but for a simple retrieval that returns a URL, it is sufficiently complete given annotations are absent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the single parameter slug is already well-defined as the station identifier from buscar_emisoras. The description does not add extra parameter semantics beyond that, so a baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns a stable streaming address for a live station, which is a specific verb+resource purpose. It distinguishes itself from siblings like buscar_emisoras (searching) and ver_emisora (viewing details) by focusing on obtaining the playable URL.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit when-to-use ('usala cuando el usuario quiera escuchar') and also warns against using the source signal directly. However, it lacks any mention of alternatives (e.g., when not to use this tool) relative to siblings, though the instruction to use it for listening is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool addresses a distinct user intent: searching for stations, playing a station, and viewing full details. The only overlap is that ver_emisora also returns the listening URL, but the descriptions clearly separate the two use cases.
All tool names are lowercase and verb-led, but the pattern is inconsistent: buscar_emisoras and ver_emisora use verb_noun, while escuchar is a bare verb. Also, buscar_emisoras is plural while ver_emisora is singular, making the naming somewhat unpredictable.
Three tools is well-scoped for a radio station directory and player server. Each tool serves a necessary, non-redundant core function: search, listen, and view details.
The primary workflow of search, inspect details, and listen is fully covered. Minor gaps exist such as no direct genre listing or popular stations endpoint, but agents can work around these with the search tool's flexible parameters.
