Skip to main content
Glama

Set built and painted model counts

set_collection_progress
Destructive

Sets a datasheet’s built and painted totals. Read get_my_collection first and use the datasheet id it returns. 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>",
      "built": "<built>",
      "painted": "<painted>"
    },
    "name": "set_collection_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
builtYes
entryIdYes
paintedYes
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 readOnlyHint=false and destructiveHint=true, and the description is consistent with that by calling it a 'set' of totals and disclosing the mcp:manage permission requirement. It adds real value beyond annotations (auth scope plus the read-before-write ordering) but does not state that existing values are overwritten rather than incremented.

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 action, then the prerequisite, then the permission. No redundant or filler wording.

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

Completeness5/5

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

For a destructive write tool with no output schema, the description covers action, prerequisite read, id source, and required scope, which is what an agent needs to call it correctly. The only minor omission is explicit overwrite semantics, which the 'set totals' phrasing and destructiveHint already imply.

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 40%, with entryId, built, and painted undocumented in the schema. The description partially compensates by equating the 'datasheet id' with entryId and identifying built/painted as the values written, but adds no range or format detail beyond the schema's own bounds.

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 uses a specific verb and resource: 'Sets a datasheet's built and painted totals,' naming both fields it writes. It is clear what the tool does, though it does not explicitly differentiate itself from siblings such as set_collection_counts_as or set_collection_models.

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?

It gives a concrete prerequisite workflow ('Read get_my_collection first and use the datasheet id it returns') and a required scope ('Requires mcp:manage'), which tells the agent how to prepare. It stops short of naming when to choose this over the closely named sibling set tools.

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