Skip to main content
Glama

Set owned model count

set_collection_models
Destructive

Sets the total number of models owned for a datasheet. Use its id from list_units or get_my_collection. Confirm the unit and count with the player. 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>",
      "models": "<models>"
    },
    "name": "set_collection_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelsYes
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

A4.1/5.0
Behavior4/5

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

Annotations already flag this as a destructive, non-read-only write, and the description adds real context on top: the mcp:manage permission requirement and the instruction to confirm before writing. The phrase 'sets the total number' signals that the existing count is replaced rather than incremented, which is the key destructive behavior. It does not describe what the response returns or what happens with an invalid entryId.

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, front-loaded with the operation, then the id source, then the confirmation and auth requirement. No filler and nothing important is buried.

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 definition covers purpose, id sourcing, confirmation, and authorization. Minor gaps remain around failure modes and whether the new count is echoed back, but nothing an agent needs to call it correctly is absent.

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 50%, with llm_model and conversation_id documented in-schema but entryId and models left bare. The description compensates by telling the agent where entryId comes from (list_units or get_my_collection) and that models is the owned count, which resolves the two required parameters that matter for correct invocation.

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 opens with a specific verb and resource: it sets the total number of models owned for a datasheet. That distinguishes it from collection tools such as set_collection_wanted or set_collection_counts_as by making clear it is an absolute owned-count setter, not a delta or a wishlist operation. It does not explicitly name a sibling it is not, so it stops short of a 5.

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

Usage Guidelines4/5

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

Usage context is clear: obtain the id from list_units or get_my_collection, confirm the unit and count with the player, and note the mcp:manage requirement. What is missing is an explicit when-not rule, such as what to do if the model is only wanted rather than owned, but the guidance is well above the minimum.

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