Skip to main content
Glama
Sign In

AtexRadio

by com.atexradio
OverviewDiscussionsAdmin

fetch_guide

Devuelve el contenido y los metadatos de una guia publica por su slug o URL, para investigacion y citacion.

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": {
      "id": "<id>"
    },
    "name": "fetch_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesslug o URL de la guia.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the load. Calling the guide 'publica' usefully signals no auth is required, and 'contenido y metadatos' discloses the return shape. It does not cover failure behavior (unknown slug/URL), content size or truncation, so gaps remain for a no-annotation tool.

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?

One compact sentence that front-loads the action and resource, then the lookup key, then the purpose. Nothing is redundant or padded.

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 lookup with no output schema, stating that both content and metadata are returned is sufficient. Only edge-case behavior for invalid identifiers is unaddressed, which is a minor omission at this complexity.

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 coverage is 100% and the single parameter is already documented as 'slug o URL de la guia'. The description restates the same dual-acceptance without adding format examples or ambiguity resolution between slug and URL, so 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 (guia publica) plus the lookup key (slug o URL) and what is returned (contenido y metadatos). It implicitly separates itself from search_guides by requiring a known identifier, though it 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Para investigacion y citacion' hints at the intended context, and 'por su slug o URL' implies you already have an identifier rather than searching. It never says when to prefer search_guides or what to do when the slug is unknown, so guidance remains implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AtexRadio toolsInspect
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