Skip to main content
Glama
Sign In

DolfDarts Dart Game Encyclopedia

by io.github.realist99
OverviewDiscussionsAdmin

Get the darts checkout for a score

get_checkout
Read-only

Get the recommended steel-tip, double-out checkout for a score from 2 to 170: the route for 3, 2 and 1 darts in hand, alternatives on other doubles, and the best setup shot when there is no finish. Bogey numbers (159, 162, 163, 165, 166, 168, 169) and scores over 170 return checkout:false with the reason. Same routes as the dolfdarts.com/checkouts/ page, whose URL is included.

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": {
      "score": "<score>"
    },
    "name": "get_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
scoreYesPoints left to finish (steel tip, double out). Checkouts exist for 2–170; anything else returns a 'no checkout' result.
dartsInHandNoDarts still in hand this visit (default 3). The result always includes the play for 3, 2 and 1 darts.
preferDoubleNoOptional favourite finish, e.g. 'D16', 'D20' or 'Bull'. Adds the best published route ending on it, when one exists.

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. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnly and non-open-world; the description goes well beyond by disclosing the failure behaviour (checkout:false with a reason for bogey numbers and >170) and the shape of a successful result (routes for 3/2/1 darts, alternatives on other doubles, setup shot when no finish). With no output schema, this is exactly the burden the description has to carry, and it does.

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?

Three sentences, front-loaded with the core purpose, and every sentence carries information (domain, edge cases, result contents, source URL). Slightly dense and the URL sentence is the least load-bearing, but there is no filler.

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 single-score lookup with three parameters, thin annotations and no output schema, the description covers scope, edge-case returns, result contents and provenance. An agent has everything needed to call it and interpret the response.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond it: it explains that every result already contains the 3/2/1-dart plays (making dartsInHand a preference rather than a filter) and that preferDouble only adds a route "when one exists". Those are non-obvious semantics the schema alone does not convey.

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 ("Get the recommended steel-tip, double-out checkout") with the exact domain (score 2–170) and the content of the answer (3/2/1 darts, alternatives, setup shot). Nothing about it overlaps with the taxonomy/game/rules siblings, so an agent can pick it out immediately.

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?

It clearly delimits the valid input space (2–170) and states what happens outside it, including the named bogey numbers, which tells the agent when the tool is applicable. It stops short of naming an alternative when a checkout is impossible (e.g., pointing to a rules or setup tool for context), so no sibling routing is offered.

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

All DolfDarts Dart Game Encyclopedia 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