Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

openligadb_current_group

Read-only

Get the source's current matchday or grouping id for one league shortcut. Use openligadb_current_matchday for those matches or openligadb_groups to list every group in a season.

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": {
      "league_shortcut": "<league_shortcut>"
    },
    "name": "openligadb_current_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
league_shortcutYesRequired exact league shortcut from openligadb_leagues, including its original case and 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. Added

TDQS

A3.8/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 safety and external-data coupling are covered. The description adds only that the output is an id for one league, with no notes on staleness, missing-current-group behavior, or case-sensitivity requirements. An output schema exists, so return structure is handled elsewhere.

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 sentences, zero filler: first sentence states what is returned and for what scope, second enumerates alternatives. Front-loaded and easy to parse.

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?

With annotations, a fully documented single parameter, and an output schema, the remaining burden is modest and the description meets it: it says this returns an id and points to the right sibling for matches or the full group list. The one gap is not clarifying whether a 'grouping id' can differ from a matchday id for the same league.

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?

Only one parameter with 100% schema description coverage, including exact-case and source-of-value guidance ('from openligadb_leagues'). The description's 'one league shortcut' reinforces the singular scope but adds no syntax or format information beyond the schema, so baseline 3 is appropriate.

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

Purpose4/5

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

States a specific verb and resource: fetch the source's current matchday/grouping id for a single league shortcut. It differentiates from two siblings by name (openligadb_current_matchday for matches, openligadb_groups for full listings). The phrase 'current matchday or grouping id' is slightly ambiguous about what exactly is returned, keeping it below a 5.

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: this tool yields the id, openligadb_current_matchday yields the matches, openligadb_groups yields every group in a season. That is clear alternative-selection guidance. It stops short of stating when the id itself is the desired output (e.g., as a follow-up parameter).

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

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources