Skip to main content
Glama

List counts

list_counts
Read-onlyIdempotent

List stock counts in this organization, newest count date first. A count compares what people scanned with the stock the system expects. Optional filters are search (part of the count name), status (open, closed, or applied), date_from and date_to (YYYY-MM-DD, inclusive, compared to the count date), folder_id, assigned_to (a user id), and sheet_number. page starts at 1. page_size defaults to 50 and is capped at 100. Returns counts with their totals (batches, scan lines, units, barcodes, comments, last scan) and the people involved (id and name only), plus total and has_more. Requires the stock plan feature. Use get_count for one count.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_counts"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
searchNo
statusNo
date_toNo
date_fromNo
folder_idNo
page_sizeNo
assigned_toNo
sheet_numberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds context beyond them: ordering, page starting at 1, page_size default of 50 capped at 100, inclusive date semantics, and a prerequisite ('Requires the stock plan feature'). It also previews the return payload including total and has_more, which is behavioral information the annotations cannot supply.

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-loaded with purpose and ordering before filters and pagination, and nearly every clause adds usable information. The filter enumeration is a dense run-on list, but it is organized with parenthetical clarifications rather than wasted prose, so it stays readable at roughly 90 words.

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 supplies the return shape (totals for batches, scan lines, units, barcodes, comments, last scan; people as id and name only; total and has_more) and the feature prerequisite. For a 9-parameter, zero-required list tool this is complete enough to call correctly without opening the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 the full burden, and it largely does: it explains search scope ('part of the count name'), the three status values, date format and inclusivity and what dates are compared to, page origin, page_size default and cap. Only folder_id and sheet_number are left as name-only labels, a minor residual gap against otherwise complete coverage.

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 stock counts in this organization') plus ordering ('newest count date first'), and defines a count in one clause so the agent knows what the resource actually is. It explicitly routes to the sibling get_count for single-record retrieval, distinguishing it from the detail tool.

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?

Clear context for when this is the right call: browsing counts with optional filters and pagination, and it names get_count as the alternative for one count. It does not address other plausible alternatives (e.g. list_unassigned_count_lists or list_count_lines), but it does provide explicit routing to the most likely confusion.

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