Skip to main content
Glama

Update count

update_count
Destructive

Change a count. Send count_id plus the fields to change. An omitted field stays as it is. null clears due_at, sheet_number, location_id, assigned_to, and folder_id. status can only be open or closed. Applying a count is done with apply_count. An applied count is read-only. Changing the sheet clears the compared lines and hand matches, so run compare_count again. 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": "update_count"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
due_atNo
statusNo
count_idYes
folder_idNo
count_dateNo
assigned_toNo
location_idNo
sheet_numberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Adds substantial behavior beyond the destructive/readOnly annotations: partial-update semantics (omitted fields stay), explicit null-clearing for five nullable fields, the allowed status values, the immutability of applied counts, and the destructive side effect of changing the sheet (compared lines and hand matches are cleared). This is exactly the kind of downstream-consequence disclosure the tool needs.

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?

Short declarative sentences ordered by importance: what it does, how to call it, merge semantics, clearing semantics, constraints, sibling routing, side effects, prerequisite. Every sentence carries a distinct fact with no padding.

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 a 9-parameter destructive mutation with no output schema, the definition covers merge behavior, null clearing, enum limits, applied-count immutability, cascade side effects, follow-up action, and license precondition. No return values are needed since the tool has no output schema.

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?

With 0% schema description coverage the description must carry the load, and it does for most parameters: null-clearing is spelled out for due_at, sheet_number, location_id, assigned_to and folder_id, and status is constrained to open/closed. However, name and count_date receive no mention, and count_date's YYYY-MM-DD format is never surfaced.

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?

"Change a count" is a specific verb+resource pair, immediately elaborated with the update contract ("Send count_id plus the fields to change"). It also explicitly separates the tool from its siblings: applying is done with apply_count, and post-sheet-change you must run compare_count again.

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 the agent to alternatives: apply_count for applying a count, compare_count for re-running comparison after a sheet change. It also states a hard precondition ("Requires the stock plan feature") and an exclusion ("An applied count is read-only").

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