Skip to main content
Glama

The Daily Smark

by com.thedailysmark

List News

list_news
Read-onlyIdempotent

List recent pro-wrestling news headlines aggregated by The Daily Smark, featured and newest first. Returns markdown links back to the original publisher, never the full article text. Keep the links in your answer so the reader can open the story. Covers roughly the last 30 days.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for paging through older headlines. Starts at 1.
limitNoHow many headlines to return (1-50). Defaults to 15.
companyNoFilter to one promotion by its code, e.g. "wwe", "aew", "nxt", "njpw", "tna", "roh", "stardom", "mlw". Omit for all promotions.
showSpoilersNoInclude headlines that give away match results. Defaults to false, so leave it off unless the user has explicitly asked for results or spoilers.

TDQS

A4.5/5.0
Behavior4/5

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

Adds context beyond annotations: returns markdown links (not full text), covers last 30 days, ordering by featured then newest. No contradiction with readOnlyHint, openWorldHint, or idempotentHint.

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?

Concise, well-structured, front-loaded with main purpose. Every sentence adds value without waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Fully describes return format, time range, ordering, and filtering options. No output schema exists, but description compensates adequately.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds value by clarifying when to use showSpoilers (only on explicit request). This extra guidance improves parameter semantics above the baseline of 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?

The description clearly states the tool lists recent pro-wrestling news headlines from The Daily Smark, with clear output details (markdown links, no full text). It is distinct from sibling tools like get_event or list_videos.

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?

Provides guidance on keeping links in answers and on using the showSpoilers parameter only when explicitly requested. Does not explicitly compare to siblings, but the purpose is unique enough to avoid confusion.

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 toolsInspect
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.

TDQS

A4.2/5.0
Disambiguation5/5

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