Skip to main content
Glama

Resolve count lines

resolve_count_lines
Destructive

Set the decision on 1 to 500 lines of a count at once. resolution is accept (use the counted number when the count is applied), recount (ask for another count), ignore (leave the stock alone), or null to clear the decision. A line can be accepted only when it has an item and a counted number. Lines that cannot are returned in skipped with the reason. Returns updated and skipped. 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>",
      "line_ids": "<line_ids>",
      "resolution": "<resolution>"
    },
    "name": "resolve_count_lines"
  }
}

Input Schema

NameRequiredDescriptionDefault
count_idYes
line_idsYes
resolutionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this as a destructive, non-idempotent mutation, and the description adds real context beyond that: partial-failure behavior ('Lines that cannot are returned in skipped with the reason'), a precondition on accept, that an applied count becomes read-only, and a feature-flag requirement. It does not explain reversibility or permission requirements beyond the feature gate, keeping it below a 5.

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?

Roughly five short sentences with no filler; the mutation scope leads, followed by value semantics, preconditions, and return shape in a logical order. Every sentence contributes a fact an agent needs.

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 three-parameter destructive mutation with no output schema, the description covers return shape (updated and skipped), failure handling, preconditions, and the feature gate, which is close to sufficient. Minor gaps remain around permissions and whether retrying the same call is safe given idempotentHint=false.

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 description coverage is 0%, so the description carries the burden and does much of it well: each resolution value (accept, recount, ignore, null) is given concrete meaning the bare enum lacks, and the line_ids range is echoed as '1 to 500 lines'. count_id is left completely unexplained and there is no indication of what identifier space line_ids belongs to, which is the main remaining gap.

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 first sentence states a specific verb-and-resource pair ('Set the decision on 1 to 500 lines of a count at once') plus the batch size limit, which is far more informative than the title alone. It does not name a sibling such as apply_count or list_count_lines to disambiguate when to prefer one over the other, so it falls 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 Guidelines3/5

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

Usage context is implied through prerequisites ('A line can be accepted only when it has an item and a counted number', 'An applied count is read-only', 'Requires the stock plan feature') rather than stated as when-to-use guidance. There is no explicit routing to alternatives (apply_count, list_count_lines, compare_count) or statement of when not to call this tool.

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