Skip to main content
Glama

Add count lists

add_count_lists

Attach count lists (batches) to a count. list_ids holds 1 to 100 lists that are in the count mode and not in another count. See list_unassigned_count_lists. The count must be compared again afterwards. An applied count is read-only. Returns the updated count. Requires the stock plan feature.

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": {
      "count_id": "<count_id>",
      "list_ids": "<list_ids>"
    },
    "name": "add_count_lists"
  }
}

Input Schema

NameRequiredDescriptionDefault
count_idYes
list_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, closed-world, and the description correctly adds plan gating ('Requires the stock plan feature'), the read-only nature of applied counts, and the required re-compare afterwards. However it does not state what happens on partial failure (e.g. one list already attached) or whether the attach is atomic across 1-100 lists, which is material for a non-idempotent mutation.

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?

Six short sentences, front-loaded with the action, then constraints, then sibling pointer, then side effects. No filler and nothing repeated from the schema.

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?

Says it returns the updated count, which covers the absent output schema, and it covers plan gating and the required follow-up compare. Still silent on error/partial-failure behavior for a non-idempotent batch mutation, which is the main thing an agent needs beyond what is given.

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 0%, so the description carries the burden; it does explain list_ids semantics well by adding eligibility rules that minItems/maxItems cannot express. count_id is left entirely implicit (which counts are valid targets, e.g. draft only, is only hinted at by 'an applied count is read-only').

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb+resource ('Attach count lists (batches) to a count') with the domain term 'count lists' glossed as 'batches'. It also names a sibling for the prerequisite lookup, so an agent can distinguish it from list_unassigned_count_lists without opening a schema.

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?

Gives the eligibility conditions for the input lists (in count mode, not already in another count) and points to list_unassigned_count_lists as the way to find candidates. It also implies a when-not condition via 'An applied count is read-only'. Missing is an explicit statement of what to do when the count is not in a comparable state.

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