Skip to main content
Glama

Set what a model collection entry counts as

set_collection_counts_as
Destructive

Replaces the alternative datasheets a unit’s models can be fielded as. Use datasheet ids from list_units. An empty list clears the alternatives. 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>",
      "countsAs": "<countsAs>"
    },
    "name": "set_collection_counts_as"
  }
}

Input Schema

NameRequiredDescriptionDefault
entryIdYes
countsAsYes
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/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, open-world write, so the bar is lower; the description still adds real value by disclosing replace-not-merge semantics, the empty-list reset behavior, and the mcp:manage authorization requirement. It does not describe failure modes or what happens to the entry if ids are invalid.

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?

Four short sentences, each carrying distinct information, with the core replace-semantics stated first and prerequisites/edge cases following. No filler or redundancy.

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 write with no output schema, the description covers the mutation semantics, the clearing behavior, the id source, and the auth scope. The remaining gap is the meaning and provenance of entryId, which an agent must guess.

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%, and the two undocumented business parameters are entryId and countsAs. The description partially compensates by explaining countsAs (alternative datasheets, sourced from list_units, empty list clears) but says nothing about entryId or how to obtain it.

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?

States a specific verb and resource: it replaces the alternative datasheets a unit's models can be fielded as, which is concrete enough to distinguish it from siblings like set_collection_models or set_collection_wanted. It does not explicitly name or contrast a sibling, 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?

Tells the agent where the countsAs values come from (datasheet ids from list_units) and documents the important edge case that an empty list clears the alternatives. It also states the required scope (mcp:manage), but gives no explicit when-not-to-use guidance or named alternative.

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