Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

openligadb_result_infos

List result types configured for a specific OpenLigaDB league ID to get league-specific result names and IDs for accurate mapping.

Instructions

List result types configured for a league. Returns the result types configured for one OpenLigaDB league id. Use this for league-specific result names and ids; openligadb_result_types lists the global machine-readable meanings.

Input Schema

NameRequiredDescriptionDefault
league_idYesOpenLigaDB league id from openligadb-leagues

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description must carry behavioral disclosure. 'List' implies a safe read and it says what is returned conceptually (result names and ids), but it omits auth needs, pagination/volume, and error behavior for a missing league id. Adequate but incomplete given the absent annotations.

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?

Front-loaded and short, but the first two sentences are near-duplicates ('List result types configured for a league' / 'Returns the result types configured for one league id'), a minor waste of a sentence.

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?

For a single-param listing tool with full schema coverage and no output schema, the description covers purpose, the update lean, and the sibling alternative. Only the shape of returned records is left implicit, a minor gap.

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 coverage is 100% and the param description already points to openligadb-leagues. The description only reiterates that it is one league-specific id, adding little syntax or format detail beyond the schema.

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 and resource ('List result types configured for a league') and explicitly names the sibling it differs from ('openligadb_result_types'), letting an agent distinguish the two without opening schemas.

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

Usage Guidelines5/5

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

Explicitly tells the agent when to use this tool ('league-specific result names and ids') versus the global alternative, which lists 'machine-readable meanings'. The routing condition is unambiguous.

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