Skip to main content
Glama

Sports / Dyscypliny

list_disciplines
Read-onlyIdempotent

Sports on KiedySport.pl with the number of upcoming events, Polish and English names, the slug to pass as discipline to search_events and the sport page link. No arguments; example call: {}. / Lista dyscyplin z liczbą wydarzeń.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_disciplines"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
okYestrue = the tool ran (also when nothing was found; read status).
statusYes
messageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety and side-effect questions are answered structurally. The description adds that the call takes no arguments and describes the record contents, but much of that overlaps the existing output schema rather than revealing new behavioral traits such as freshness of counts or ordering.

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-loads the payload contents before the empty-argument note, and the bilingual restatement matches the site's audience. The Polish sentence largely duplicates the English one, which costs a little efficiency but is not harmful.

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?

For a zero-argument, read-only listing tool with a declared output schema and full annotation coverage, the description supplies everything needed: what is returned, that no inputs exist, and how the returned slug feeds the sibling search tool.

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?

Zero parameters, which is the baseline-4 case, and the description explicitly confirms 'No arguments; example call: {}', removing any doubt about needing a payload. Nothing further can be said about parameter meanings here.

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 the specific resource (sports disciplines on KiedySport.pl) and what each record carries: upcoming-event counts, Polish/English names, slug, and sport page link. It also distinguishes itself from the sibling search_events by explaining that the slug is an input to that tool, so an agent can place it in a workflow without further inference.

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?

Implies a clear discovery-then-search flow by telling the agent the slug is what you pass to search_events, and notes there are no arguments with an example call of {}. It stops short of an explicit when-to-use/when-not statement, but the sequencing guidance is unambiguous enough for correct invocation.

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.

Resources