Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

espn_soccer_scores

Read-onlyIdempotent

Fetch soccer scores from ESPN for a specified league ID, such as eng.1 or usa.1, to check match results.

Instructions

Get soccer scores from ESPN.

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_soccer_scores"
  }
}

Input Schema

NameRequiredDescriptionDefault
leagueNoe.g. eng.1, usa.1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description adds nothing beyond that: no indication of data freshness (live vs. cached), no note that omitting league changes scope, no rate-limit or coverage caveats.

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?

One short, front-loaded sentence with no filler. It is efficient, though the terseness borders on under-specification rather than genuine economy.

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

Completeness3/5

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

The tool is low complexity with one documented parameter and no output schema, so much of the burden is lifted. Still, the description leaves open what time window the scores cover and what the default behavior is without a league, which an agent needs in order to trust the result.

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 description coverage is 100% and the single optional parameter 'league' is documented in-schema with examples (eng.1, usa.1). The description adds no meaning on top, so the baseline of 3 applies — notably it never explains what happens when league is omitted.

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?

The verb+resource (get soccer scores) is stated, but it is essentially an expansion of the tool name and gives no scope: nothing says whether these are live scores, today's fixtures, or final results. It also does nothing to distinguish itself from the parallel espn_nfl_scores / espn_nba_scores / espn_mlb_scores siblings beyond the sport word already in the name.

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 pick this over the ESPN siblings or over sportsdb_* / esports_* alternatives, and no mention of any preconditions such as needing a valid league slug. The agent must infer everything from the tool name.

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