Skip to main content
Glama
Sign In

Morris Golf

by golf.morris
OverviewDiscussionsAdmin

Measure priority

measure_priority
Read-onlyIdempotent

Measure the player's active training priority again now: the same figure, computed the same way against the same reference, over the rounds played since it started, against the starting figure. It says better, same or worse only when the change passes the margin, and otherwise how many rounds are missing. Use it when the player reports a new round; to read the priority, its exercise and its history use get_priority. With no active priority there is nothing to measure: say nothing about it. Read-only.

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": "measure_priority"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered; the description adds real substance on top by explaining the margin-gated outcome semantics (better/same/worse only when the change passes the margin) and the fallback output of remaining rounds. It also discloses the silent-no-op edge case, which is behavior the agent could not infer from annotations.

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?

The trigger and the sibling routing come early, and every sentence carries information, including the terminal 'Read-only' confirmation. The opening clause ('the same figure, computed the same way against the same reference') is somewhat repetitive and slows comprehension slightly.

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?

With no parameters and no output schema, the description carries the full burden and does so: it explains what is compared, the qualitative result vocabulary, the margin gating, the alternate output when insufficient rounds exist, and the no-active-priority case. Nothing an agent needs to call it or report its result is missing.

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?

The tool takes zero parameters, so there is no parameter semantics to add and the baseline of 4 applies. The description correctly implies no arguments while emphasizing it operates on the current active priority implicitly.

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?

The description states a specific verb-plus-resource ('measure the player's active training priority again now') and pins down the computational basis: same figure, same reference, rounds since it started versus the starting figure. It also explicitly distinguishes itself from the sibling reader tool get_priority, so an agent can route without opening either schema.

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

Usage Guidelines5/5

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

It gives a concrete trigger ('when the player reports a new round'), names the alternative for the other case ('to read the priority, its exercise and its history use get_priority'), and states the no-op condition ('with no active priority there is nothing to measure: say nothing about it'). When-to-use, when-not-to-use, and the alternative are all explicit.

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

All Morris Golf 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