Crawlora MCP

openligadb_goal_getters

Read-only

Get OpenLigaDB's goal-getter ranking for one discovered league and season. Use openligadb_match for goal events in a single match.

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>",
      "season": "<season>"
    },
    "name": "openligadb_goal_getters"
  }
}

Input Schema

Name	Required	Description	Default
`season`	Yes	Required season starting year, such as 2026 for 2026/27; discover supported combinations with openligadb_leagues.
`league_shortcut`	Yes	Required exact league shortcut from openligadb_leagues.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

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 the safety profile is covered. The description adds only the scoping constraint (one league + season); it says nothing about result ordering, tie-breaking, or what a missing/unsupported season yields. With an output schema present, return shapes need not be described, so a 3 is appropriate.

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 short sentences, no padding, with the purpose front-loaded and the disambiguation sentence last. Every clause earns its place.

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 two-parameter, read-only ranking lookup with full schema coverage, annotations, and an output schema, the description covers what an agent needs to select and call it. It falls just short of full completeness by omitting any note on season-format edge cases or what an unknown league returns.

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%: both league_shortcut and season already carry descriptions, including the season-year convention and the pointer to openligadb_leagues. The description just echoes 'one discovered league and season' without adding format or validation detail, which is the expected baseline when the schema does the work.

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 (retrieve the goal-getter / top-scorer ranking) and pins the scope to a single league and season. It also names the sibling it is not (openligadb_match), so an agent can separate season-wide scorer rankings from per-match goal events.

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?

Gives a clear routing rule: use this for the league/season scorer ranking, use openligadb_match for goal events in a single match. The prerequisite that the league/season must already be 'discovered' is implied here and spelled out in the schema, but no explicit error/edge-case guidance is given.

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

All Crawlora MCP tools Inspect

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.