Skip to main content
Glama

Get score

get_score
Read-onlyIdempotent

Retrieve a player's or label's score for a specified Minecraft scoreboard objective, returning 0 when no score exists.

Instructions

A score holder's score on an objective (0 if they have none).

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>"
    },
    "name": "get_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description contributes one real behavioral detail beyond that: a missing score returns 0 rather than an error. It says nothing about what happens when the objective itself does not exist, which would be the next useful disclosure.

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 short sentence with the subject front-loaded and zero wasted words. It is arguably too terse for the tool's semantics, but nothing in it is redundant.

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 a full output schema, rich read-only annotations, and 100% schema coverage on two required params, the description covers purpose and the zero-default behavior. The only meaningful gap is error behavior for an unknown objective, a minor omission for a simple read tool.

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%, with both player (including the '#timer' label example) and objective fully documented in the schema, so the baseline is 3. The description only restates that a score holder and an objective are involved, adding no format or constraint detail beyond the schema.

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?

States a specific resource (a score holder's score on an objective) and implicitly the read verb, which clearly distinguishes it from the sibling set_score. It does not explicitly name any sibling, so it falls short of the 5 bar.

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

Usage Guidelines2/5

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

The description contains no when-to-use, when-not-to-use, or alternative-tool guidance. Usage is only inferable from the name get_score and the read-only nature of the annotations, which is below the implied-usage bar for a 3.

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