Skip to main content
Glama
livetennisapi

livetennisapi-mcp

by livetennisapi
OverviewSchemaRelated ServersScoreDiscussions
JavaScript

API status and plan

check_api_status
Read-onlyIdempotent

Verify if the Live Tennis API is accessible and identify the plan tier of your API key to diagnose data retrieval issues.

Instructions

Check whether the Live Tennis API is reachable and which plan the configured key is on. Useful for diagnosing why other tools are refusing data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesTrue when the call returned data. False for a tier wall, a missing or rejected key, or an empty result — all of which are normal states with a clear remedy, not failures.
tierNoDetected plan: FREE, BASIC, PRO or ULTRA. Null when no key is configured.
has_keyNoWhether a key was supplied with this call.
messageYesHuman-readable summary. Identical to the text content, so either half can be used alone.
reachableNoTrue when the API answered its health check.
api_versionNoAPI version reported by the health check.

Tool Definition Quality

A4.5/5.0
Behavior4/5

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

Annotations already provide strong behavioral hints (read-only, idempotent, non-destructive). Description adds specific context (reachability, plan check) without contradicting. High transparency overall.

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?

Extremely concise: two sentences, front-loaded with action, no unnecessary words.

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?

Low complexity: no parameters, output schema exists, annotations rich. Description efficiently conveys purpose and diagnostic context. Complete.

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?

No parameters, so description is not required to elaborate on param semantics. Schema coverage is 100% (empty schema). Baseline score of 4 applies.

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?

Clear verb+resource: 'Check whether the Live Tennis API is reachable and which plan'. Distinguishes from sibling data-fetching tools (get_fixtures, get_match, get_upcoming_matches) by being a diagnostic tool.

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 context on when to use ('diagnosing why other tools are refusing data'), but does not explicitly state exclusions or alternatives. Given simplicity, this is adequate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/livetennisapi/livetennisapi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server