Skip to main content
Glama
Sign In

GradeTV

by net.gradetv
OverviewDiscussionsAdmin

Get API X402 programacao by slug

get_api_x402_programacao_by_slug

The last seven days of the channel's schedule in one call, for an agent, paid per call, with no account. Select the title or category across collected days and receive calendar events with absolute times. You do not need to merge daily records and write a calendar exporter. Only collected dates are returned. This is metadata, not a video archive, a broadcast license or a guarantee that a channel plays.

Input Schema

NameRequiredDescriptionDefault
slugYesStored slug of the channel, from the collection.
agendaNoInclude agenda_ics with the selected calendar events.
programaNoTitle or category substring. Input and matches are not truncated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / agenda
      Added value: +{
+  "description": "Include agenda_ics with the selected calendar events.",
+  "enum": [
+    "1"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / programa
      Added value: +{
+  "description": "Title or category substring. Input and matches are not truncated.",
+  "type": "string"
+}
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations it discloses billing ('paid per call'), the absence of an account requirement, the data boundary ('Only collected dates are returned'), and negative scope (not a video archive, not a broadcast license, not a playback guarantee). That explains why readOnlyHint is false despite a read-shaped operation (the payment side effect) without contradicting it.

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

Conciseness4/5

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

The key capability and scope are front-loaded in the first sentence, and each following sentence adds a distinct constraint or disclaimer. The closing caveat chain ('metadata, not a video archive, a broadcast license or a guarantee') is a touch listy but still earns its place as scope limiting.

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 return-shape burden and does so: calendar events with absolute times, limited to collected dates within a seven-day window. What is missing is mainly pagination/volume expectations and the exact form of agenda_ics when agenda=1 is set.

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%, so all three parameters are already documented, including the programa substring and the agenda enum. The description adds little beyond that: 'Select the title or category' loosely echoes the programa schema text, and 'calendar events' hints at agenda, but slug sourcing and the enum value are left entirely to the schema.

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?

The description states a specific verb and resource: a single call returning the channel's last seven days of schedule keyed by slug. It implicitly contrasts with the per-day sibling get_api_x402_programacao_by_slug_by_dia ('You do not need to merge daily records'), but never names that sibling directly, so differentiation relies on inference.

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?

It gives clear operating context: one call instead of stitching daily records, an agent-oriented, paid-per-call, no-account model. It omits an explicit 'use X instead when...' clause naming the day-by-day or list_programacao alternatives, so there is no stated exclusion, only positive guidance.

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

All GradeTV 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