The Daily Smark

Get Tv Schedule

get_tv_schedule

Read-onlyIdempotent

Get the pro-wrestling TV schedule: which shows air on which days, on which channels. Use this to answer "what is on tonight/this week".

Input Schema

TableJSON Schema

Name	Required	Description
`company`	No	Filter to one promotion by its code, e.g. "wwe", "aew". Omit for all promotions.
`numDays`	No	How many days forward from startDate to include (1-96). Defaults to 7.
`singleDay`	No	Return only shows airing on startDate itself. Defaults to false.
`startDate`	No	Day to start from, as YYYY-MM-DD. Defaults to today.

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint. The description confirms it's a read operation but adds no new behavioral traits beyond 'get the schedule'.

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?

Two sentences with zero waste. First sentence defines purpose, second gives usage context. Well front-loaded.

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?

Adequate for a read-only scheduled tool with optional parameters. No output schema, but the description is clear enough given the annotations and parameter richness.

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 provides descriptions for all 4 parameters, and the tool description does not add further meaning beyond what's in the schema. Baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the tool retrieves the pro-wrestling TV schedule, specifying shows, days, and channels. Distinguishes itself from siblings like get_event.

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?

Explicitly tells the agent to use it for answering 'what is on tonight/this week', but does not mention when not to use or suggest alternatives.

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

All The Daily Smark tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Each tool targets a distinct resource: event details, TV schedule, live events, news, podcasts, and videos. The descriptions clearly differentiate them, and any overlap (e.g., get_event vs list_live_events) is explicitly resolved by referencing earlier steps.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern: get_ for single resources and list_ for collections. This makes the API predictable and easy for agents to select the correct tool.

Tool Count5/5

Six tools is well-scoped for a content aggregation server covering news, media, and events. Each tool earns its place without excess or redundancy, fitting the typical recommended range.

Completeness5/5

The tool surface covers the full consumption workflow: browsing schedules, discovering events, retrieving event details, and accessing news, podcasts, and videos. There are no obvious dead ends for the read-only purpose of this server.

Resources

Need Help?