Skip to main content
Glama

List count lines

list_count_lines
Read-onlyIdempotent

List the compared lines of a count, one per barcode or item, paged. Run compare_count first. Each line has counted (what people scanned), expected (the stock the system had when compare_count last ran, not the stock now), variance, and the decision (accept, recount, ignore, or none). variance = counted minus expected, so a negative variance means fewer were counted than expected. A counted of null means the line has not been counted yet. It does not mean zero. Optional filter is all (default), variance, matched, not_found, multiple, not_counted, unresolved, accept, recount, or ignore. search matches part of the scanned barcode. page starts at 1. page_size defaults to 100 and is capped at 200. Lines are paged, so check pagination.totalPages before saying something is missing. Returns the lines, pagination, the summary, and comparedAt. 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>"
    },
    "name": "list_count_lines"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
filterNo
searchNo
count_idYes
page_sizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the safety profile is covered. The description adds meaningful context beyond that: expected is a snapshot from the last compare_count rather than current stock, null means not counted rather than zero, variance is counted minus expected, and the tool requires the stock plan feature. It does not explain rate limits or ordering, but the added behavioral detail is substantial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core purpose, then layers the field semantics before the paging and filter details. It is dense but nearly every sentence adds operative information; the filter enumeration is long but necessary given the 0% schema coverage.

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?

With no output schema, the description compensates by naming what is returned (lines, pagination, summary, comparedAt) and warning that lines are paged so pagination.totalPages should be checked before concluding data is missing. For a five-parameter read tool this is complete enough to call correctly.

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 must carry parameter meaning, and it largely does: it enumerates the filter values, explains that search matches part of the scanned barcode, states page starts at 1, and gives the page_size default of 100 and cap of 200. count_id is left unexplained, which is the only notable gap.

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?

States a specific verb and resource: list the compared lines of a count, one per barcode or item, paged. It also names the prerequisite tool (compare_count) and the per-line fields, so an agent can distinguish it from siblings like get_count or resolve_count_lines 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 a clear precondition ("Run compare_count first") and explains the filter values and search behavior, which is genuine when-to-use guidance. It does not name alternative tools for other views (e.g. comments or unassigned lists), but it makes the context of use unambiguous.

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