Skip to main content
Glama

Remove count list

remove_count_list
Destructive

Take one batch out of a count. The list and its scans are kept and become unassigned. The count must be compared again afterwards. An applied count is read-only. 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_id": "<list_id>"
    },
    "name": "remove_count_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
list_idYes
count_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

With destructiveHint=true already declared, the description adds non-obvious consequences the annotation cannot convey: the list and its scans survive as unassigned rather than being deleted, and the count becomes stale until re-compared. It also discloses a licensing prerequisite and a read-only state that blocks the operation. This is exactly the context an agent needs before a destructive call.

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 a distinct fact: the action, the retention behavior, the follow-up requirement, the read-only guard, plus the feature requirement. The consequence is front-loaded right after the verb with no filler.

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 two-param destructive mutation with no output schema, the description covers effect, side effects, post-call requirement, blocking state, and licensing. It omits only error behavior (what happens if the count is applied) and whether the batch can be re-added via add_count_lists, which would round it out.

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 description coverage is 0% for two required params, count_id and list_id. The description implies the mapping (count_id = the count, list_id = the batch removed) but never states formats, identifiers, or how to obtain either value. Adequate inference, not documented semantics.

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: taking one batch (list) out of a count. 'The list and its scans are kept and become unassigned' pins down that this detaches rather than deletes. It doesn't explicitly name a sibling or contrast itself with add_count_lists / list_unassigned_count_lists, so differentiation is inferred rather than stated.

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 real preconditions: the count must be applied-checked ('must be compared again afterwards') and an applied count is read-only, so the call is blocked in that state. The stock-plan-feature requirement is another gating condition. What's missing is an explicit alternative or 'use this when' framing relative to add_count_lists or list_unassigned_count_lists.

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