Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

espn_news

Read-onlyIdempotent

Fetch ESPN sports news by sport and limit results, so you can quickly gather current headlines for a specific sport or general coverage.

Instructions

Get ESPN sports news.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "espn_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sportNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds nothing beyond that: no mention of news source, freshness, regional coverage, pagination, or return format. With annotations carrying safety, the description still contributes no behavioral context.

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

Conciseness3/5

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

The single sentence is front-loaded and free of waste, but it is too sparse to provide any structure for a tool with two undocumented parameters. Brevity here is under-specification rather than effective conciseness.

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

Completeness2/5

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

Given two parameters with 0% description coverage, no output schema, and a large sibling set, the description is materially incomplete. It does not explain the sport filter, the limit, or what news content is returned, leaving the agent to call it largely blind.

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

Parameters1/5

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

There are two parameters (limit and sport), and schema description coverage is 0%. The description mentions neither parameter, so an agent cannot infer valid values (e.g., which sport names are accepted) or the meaning of limit from any source.

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

Purpose3/5

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

It states a verb and resource ('Get ESPN sports news'), so the intent is discernible. But it does not distinguish what kind of news (headlines, articles, recaps) or how it differs from the many ESPN score tools and general news tools in the sibling list. The purpose is vague rather than misleading.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus the ESPN score siblings or news_top_headlines/news_search. No exclusions, no alternatives, no context about freshness or scope. The agent is left to guess.

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

Deploy Server

Other Tools