Skip to main content
Glama

sportskeeda_taxonomy_search

Read-only

Search Sportskeeda's public category, event, team, player, wiki, and wiki-tag taxonomy for a phrase. Use sportskeeda_wiki_categories for the full wiki taxonomy or sportskeeda_sections and sportskeeda_sitemaps for broader discovery.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "Query": "<Query>"
    },
    "name": "sportskeeda_taxonomy_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
QueryYesSearch phrase; punctuation is replaced with spaces and the result is capped at 100 characters

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / Query / description
      Added value: +"Search phrase; punctuation is replaced with spaces and the result is capped at 100 characters"
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the scope of the taxonomy searched but no additional behavioral context such as result caps, matching behavior, or what the taxonomy entries represent. Adequate but not rich beyond the annotations.

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 tight sentences, front-loaded with the verb and resource, followed by routing guidance. Zero filler and no redundancy.

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?

An output schema exists, so return values need not be explained, and annotations carry the safety profile. For a single-parameter search tool the description is essentially complete, with only minor room for detail on match behavior.

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% — the single Query parameter already documents that punctuation is replaced with spaces and results are capped at 100 characters. The description only restates 'for a phrase', adding nothing beyond the schema, so the baseline 3 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?

States a specific verb ('Search') plus the exact resource ('Sportskeeda's public category, event, team, player, wiki, and wiki-tag taxonomy') and enumerates the taxonomy types covered. It also names the sibling tools it is not, so an agent can distinguish it without opening other schemas.

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 routes the agent to alternatives: sportskeeda_wiki_categories for the full wiki taxonomy, and sportskeeda_sections / sportskeeda_sitemaps for broader discovery. It gives clear context and alternatives, though it doesn't state an explicit when-not condition (e.g., that this is a phrase lookup rather than a listing).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.