Skip to main content
Glama

Get count

get_count
Read-onlyIdempotent

Get one stock count: its details, status, location, people, batches (the scan lists attached to it), follow-up recounts, barcodes matched by hand, and the line summary from the last compare. The summary is empty or zero until compare_count has run. Use list_count_lines to read the lines. 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": "get_count"
  }
}

Input Schema

NameRequiredDescriptionDefault
count_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, read-only, closed-world operation. The description adds meaningful domain behavior: the summary depends on compare_count having run, and the stock plan feature is required. It does not cover not-found behavior or finer permission details, but that is a minor gap given the annotations.

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?

It is front-loaded with the main purpose and every listed return detail adds useful information. There is no filler or redundant restatement of annotations.

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 low-complexity read with no output schema, the description is strong: it lists returned contents, dependencies, and a prerequisite. The remaining gap is count_id semantics, which is not documented anywhere.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The sole parameter count_id has 0% schema description coverage, and the description never states its format, source, or how to obtain it. The phrase 'one stock count' implies the parameter identifies a count, but this does not compensate for the missing schema documentation.

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 ('Get one stock count') and enumerates the returned sub-resources (batches, recounts, barcodes, line summary). It also distinguishes itself from list_count_lines, so an agent can select it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly routes line-reading to list_count_lines and notes that the summary remains empty or zero until compare_count has run. It also gives the stock plan feature prerequisite, covering both usage context and precondition.

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