Skip to main content
Glama

Set a wishlist model count

set_collection_wanted
Destructive

Sets how many more models the player wants for a datasheet. Use its id from list_units; zero clears it. Requires mcp:manage.

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": {
      "entryId": "<entryId>",
      "wanted": "<wanted>"
    },
    "name": "set_collection_wanted"
  }
}

Input Schema

NameRequiredDescriptionDefault
wantedYes
entryIdYes
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and openWorldHint=true, and the description adds concrete meaning to that: zero is the clearing operation, and the call requires the mcp:manage scope. That is useful context beyond the structured fields, though it says nothing about rate limits or side effects on other collection data.

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?

Three short sentences, front-loaded with the action, then the id source, then the permission requirement. Nothing is padded, though the term 'datasheet' is used without definition.

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?

For a destructive single-field mutation with no output schema, the description supplies the key facts: what is changed, where the id comes from, the clearing convention, and the required auth scope. Missing only return behavior and interaction with the other collection setters.

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

Parameters4/5

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

Schema coverage is only 50%, but the description covers the two required parameters: entryId is the id obtained from list_units, and wanted is the count where zero clears. The remaining two parameters carry their own schema descriptions, so the gap is adequately filled.

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 and resource: it sets how many more models the player wants for a datasheet, i.e. a wishlist target count. It is clear on its own, but it does not distinguish itself from the many sibling setters such as set_collection_models or set_collection_counts_as.

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 provides a prerequisite and provenance for the identifier ('use its id from list_units') plus the semantic that zero clears the entry, which implies when to use it. It stops short of stating when to prefer this over the adjacent collection-setting tools or any exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources