Skip to main content
Glama

copy_play_records

Copies Play Records from one game copy to another empty copy, requiring the target to have no existing Play Records.

Instructions

Copy the Play Records of one copy to another copy of the same game. The target must have no Play Records yet.

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": {
      "slug": "<slug>",
      "from_collection_id": "<from_collection_id>",
      "to_collection_id": "<to_collection_id>"
    },
    "name": "copy_play_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
to_collection_idYes
from_collection_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does disclose that this is a mutating copy operation and that the destination must be empty (implying a failure mode), and 'copy' reasonably implies the source records are retained. However, it says nothing about required permissions, atomicity on partial failure, or what happens if the precondition is violated.

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 sentences, zero padding, with the core action front-loaded and the precondition following. Every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained. For a three-parameter, fully required mutation with no schema descriptions and no annotations, the definition is adequate but thin: it leaves error behavior and the meaning of the collection IDs to inference.

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 coverage is 0%, so the description must compensate. It does imply that from_collection_id and to_collection_id identify the two copies and that slug identifies the game, which is more than the bare titles give. It still does not explain ID formats or whether slug must match an existing copy, so the compensation is partial.

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 gives a specific verb (copy) and resource (Play Records) plus a scoping constraint (between copies of the same game), which is clearly distinct from siblings like add_play_session or share_play_records. It does not explicitly name an alternative tool, which keeps it at 4 rather than 5.

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?

It states a precondition that gates usage: the target copy must have no Play Records yet. That is useful for deciding whether a call will succeed, but there is no guidance on when to prefer this over manual entry via set_play_record or add_play_session, nor any explicit exclusions.

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