Skip to main content
Glama

Create count

create_count

Create a stock count. name is required. Optional count_date (YYYY-MM-DD, default today), sheet_number, location_id (a location of that sheet), assigned_to (a user id in this organization), due_at (date and time), folder_id, and list_ids (up to 100 unassigned count lists to attach, see list_unassigned_count_lists). Returns the new count. Next: add scans or lists, then run compare_count. 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": {
      "name": "<name>"
    },
    "name": "create_count"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
due_atNo
list_idsNo
folder_idNo
count_dateNo
assigned_toNo
location_idNo
sheet_numberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false), so the description's job is to add context, which it does: it discloses the stock plan feature requirement, the default count_date of today, the 100-list cap, the constraint that location_id must belong to the given sheet and assigned_to must be an org user, and that the new count is returned. It does not discuss failure modes or what happens on invalid list_ids, 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.

Conciseness4/5

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

Front-loaded with the core action, then the required parameter, then optionals, then return value and next steps, then the prerequisite. The telegraphic fragments are dense but every clause carries information. Minor readability cost from packing defaults, constraints, and a cross-reference into a single run of parentheticals.

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?

For an 8-parameter mutation tool with no output schema and no schema descriptions, the description covers the required field, every optional field's meaning, defaults and caps, the return value, the prerequisite, and the follow-up workflow. Nothing an agent needs in order to invoke it correctly is missing.

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 carries the full burden and largely succeeds: it marks name as required, gives count_date's format and default, constrains location_id and assigned_to, caps list_ids at 100 unassigned lists and routes to the sibling that enumerates them, and clarifies due_at as a date and time. Only folder_id is left as a bare name, which is negligible against seven well-annotated parameters.

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 ('Create a stock count') and immediately scopes it against siblings by pointing to list_unassigned_count_lists for the lists to attach and compare_count as the downstream step. An agent can distinguish this creation tool from add_count_scans, add_count_lists, and compare_count without opening any 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 concrete workflow: create, then add scans or lists, then run compare_count, and directs the agent to list_unassigned_count_lists for valid list_ids. It also names the stock plan feature prerequisite. It stops short of explicit when-not-to-use or exclusion guidance, so it is clear context rather than full routing logic.

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