Skip to main content
Glama

share_play_records

Share play records between two copies of the same game, or stop sharing, by specifying the game slug and source/target collection IDs.

Instructions

Share the Play Records of one copy with another copy of the same game (share=true), or stop sharing with that copy (share=false).

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

Input Schema

NameRequiredDescriptionDefault
slugYes
shareNo
to_collection_idYes
from_collection_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries the whole burden. It usefully discloses that the operation is reversible via share=false and that both collections must be copies of the same game, but it says nothing about required permissions/ownership, whether an existing share is replaced, or any side effects on records already present in the target copy.

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 no filler, and the boolean modes are tucked into parentheses where they belong. It is efficient, though the brevity comes partly at the cost of the missing parameter detail.

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

Completeness2/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. Still, for a cross-collection state-changing operation with three required identifier parameters, zero annotation coverage, and 0% schema coverage, the description leaves too much for the agent to guess about prerequisites and identifier roles.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% — all four parameters carry only bare titles. The description clarifies the `share` boolean and its default-on semantics, but leaves `slug`, `from_collection_id`, and `to_collection_id` uninterpreted, and does not state explicitly which id is the source and which is the destination, despite that directionality being the crux of the operation.

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 pair (share / stop sharing) and a specific resource (play records), plus the relationship it operates on — between two copies of the same game. That is enough to tell it apart conceptually from copy_play_records or list_play_records, though no sibling is actually named.

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?

The parenthetical does explain when each mode applies (share=true to share, share=false to stop sharing), which is real usage guidance for the boolean. However, it gives no guidance on when this tool is preferable to copy_play_records or how it relates to list/get play-record tools.

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