Skip to main content
Glama

Stock Count Adjustment

bpj_stock_count_adjustment
Read-onlyIdempotent

Compare physical count with book inventory and value the signed quantity correction at unit cost.

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": {
      "book": "<book>",
      "physical": "<physical>",
      "standard": "<standard>"
    },
    "name": "bpj_stock_count_adjustment"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookYes
physicalYes
standardYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world, so the safety profile is fully covered. The description adds the conceptual behavior (compare, take signed difference, multiply by unit cost) but omits the sign convention (physical minus book, or vice versa) and does not say what is returned, leaving some behavioral gaps.

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?

A single front-loaded sentence with no filler; every clause describes part of the computation. It is efficient, though the terseness leaves the formula and output underexplained.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no parameter descriptions, the description should state what the tool returns (variance quantity and/or extended value) and the sign convention. Given three required numeric inputs and a computed result, the current one-liner is thin for correct invocation and interpretation.

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

Parameters3/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 load, and it does map the three inputs conceptually: physical count, book inventory, and unit cost. It does not clarify that 'standard' is a purchase unit price per unit, nor units/rounding, so compensation is only partial.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names specific operations (compare physical count vs. book inventory, value the signed correction at unit cost), which identifies the computation clearly. It does not explicitly differentiate from siblings like bpj_cycle_count_workload or bpj_design_stock_batch_weight, but the purpose itself is unambiguous.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool, no prerequisites, and no reference to alternatives. The agent must infer from the name and description alone that this is the variance-valuation computation rather than a general stock tool.

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.