Skip to main content
Glama

Set score

set_score
DestructiveIdempotent

Sets a score holder's score on a Minecraft objective, replacing the previous value.

Instructions

Set a score holder's score on an objective, replacing the previous value.

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": {
      "objective": "<objective>",
      "player": "<player>",
      "score": "<score>"
    },
    "name": "set_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
scoreYesNew score.
playerYesScore holder: a player name or any label like '#timer'.
objectiveYesObjective name (no spaces).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is known. The phrase 'replacing the previous value' usefully confirms exactly what is destroyed and reinforces idempotency, but nothing is said about error behavior for a missing objective or about the response.

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?

A single front-loaded sentence with zero filler; the overwrite behavior is stated last, which is the right priority order. It is arguably terse for a mutation tool, but nothing is wasted.

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 rich annotations, a full-coverage schema, and an output schema present, the description only needs to convey purpose and overwrite semantics, which it does. The remaining gap is whether the objective must pre-exist, which is meaningful for a destructive setter but is a minor omission.

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%, so all three parameters (objective, player, score) are already documented in the schema, including the '#timer'-style label hint for score holders. The description adds no format, range, or constraint detail beyond that, so the baseline of 3 applies.

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 names a specific verb and resource ('Set a score holder's score on an objective') and clarifies the effect on prior state, so an agent can distinguish it from the read-side sibling get_score without opening the schema. It stops short of naming that sibling explicitly, so it is clear but not fully differentiated.

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: the tool is for assigning a score on an existing objective. There is no statement of when to prefer this over get_score for reads, no precondition that the objective must already exist, and no note about whether a new score holder label is created implicitly.

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