Skip to main content
Glama

Move a wishlist pair to the collection

stockroom_mark_bought

Record a wishlist pair as bought, store the price paid, and use the pair id from stockroom_search; an owner token is required.

Instructions

Record that a wishlist pair was bought, with the price paid. Give the pair id from stockroom_search. Needs the owner token.

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": {
      "id": "<id>"
    },
    "name": "stockroom_mark_bought"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPair id from stockroom_search
pricePaidNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare the mutation-and-safety profile (readOnlyHint false, destructiveHint false, openWorldHint false), so the bar is lower. The description still adds real value by disclosing the owner-token auth requirement and the price-paid input, but it omits what happens on a pair not in the wishlist, whether repeat calls are idempotent, and that the pair moves into the collection.

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?

Three short sentences, purpose first, then the id source, then the credential requirement. No filler, and the most load-bearing constraint is front-loaded.

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?

There is no output schema, so the description must carry the result burden, and it does not say what is returned or confirmed. For a two-parameter mutation with half its schema undocumented, it leaves the pricePaid format and the post-purchase state change unexplained.

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 50%: id is already documented in the schema and the description only repeats its provenance. pricePaid has no schema description and the description says merely 'with the price paid', giving no format or unit guidance (raw number vs formatted credit string), so meaning is only partly added.

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: record that a wishlist pair was bought, with the price paid. It partly distinguishes itself from siblings by naming stockroom_search as the source of the id, but it does not contrast with stockroom_add_pair or gt7_set_owned, and the collection-moving effect is only in the title, not the description.

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 implied: call this after a purchase, passing an id obtained from stockroom_search. There is no explicit statement of when not to use it or which sibling to prefer for adjacent cases, so the agent must infer the workflow boundary.

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