Skip to main content
Glama

DolfDarts Dart Game Encyclopedia

List dart games by facet

list_games
Read-only

List dart games filtered by category, mechanic, difficulty, and/or featured flag. Returns slug, name, category, difficulty, and dolfdarts.com URL for each.

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_games"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax games to return (default: all matches). The result reports the true `total`.
categoryNoFilter: game category.
featuredNoFilter: only featured games.
mechanicNoFilter: core game mechanic.
difficultyNoFilter: difficulty level.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max games (default 200 = all)."New value: +"Max games to return (default: all matches). The result reports the true `total`."
    • changedInput schema / properties / limit / maximum
      Previous value: -200New value: +9007199254740991
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds value beyond them by enumerating the returned fields (slug, name, category, difficulty, URL), which matters because no output schema exists; it does not mention that limit truncates results while total reports the full count.

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: the filtering capability is front-loaded and the return shape follows. Nothing is redundant and nothing needs re-reading.

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 no output schema, the explicit return-field list is what an agent needs, and all five params are documented in the schema. The remaining gap is routing guidance relative to search_games and whether multiple filters are ANDed, which 'and/or' only partially addresses.

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%, and each of the four filter parameters has an enum plus its own description, so the schema does the heavy lifting. The description merely restates the filter dimensions and adds no combination semantics or enum meaning beyond what is structured.

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?

The description states a specific verb and resource ('List dart games') plus the exact filter facets, so an agent knows precisely what it retrieves. It stops short of distinguishing itself from the sibling search_games, leaving the faceted-vs-text-search boundary implicit.

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

Usage Guidelines3/5

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

Usage is only implied: 'filtered by category, mechanic, difficulty, and/or featured flag' suggests faceted browsing, but the description never says when to pick this over search_games, get_related_games, or recommend_games, nor any exclusions.

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