Skip to main content
Glama
Sign In

Conecto

by chat.conecto
OverviewDiscussionsAdmin

Count a location

inventory_stocktake

Record a count of one location: each difference from what the moves left there becomes a count move (found stock comes in at the moving average, missing stock leaves at it), so the stock matches what was counted. With full: true, items held there but left out of counts were not found (counted 0). Costs $0.002 per line counted; nothing if none are found.

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": {
      "counts": "<counts>"
    },
    "name": "inventory_stocktake"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD
fullNo
noteNo
countsYes
locationNoA location by name. Default: "Main" (made on first use).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations (non-read-only, non-idempotent), it discloses the side effect that differences are written as count moves valued at the moving average, the full:true zeroing behavior, and a per-line cost of $0.002. Reversibility and required permissions are not addressed, which keeps 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?

Three tight sentences, front-loaded with the core action, and each one carries distinct information (mechanism, full mode, cost). The moving-average parenthetical is dense but earns its place by explaining valuation.

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

Completeness3/5

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

For a mutation tool with a nested counts array and no output schema, the description never indicates what is returned (created count moves, a summary) nor what 'date' affects. It covers the write semantics well but leaves the response and backdating behavior to inference.

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 40%, so the description must compensate. It does explain 'full' thoroughly and clarifies that counts refer to items in the location (with 0 meaning not found), but 'date', 'note', and the units/format of 'counted' (number or string) are left entirely to the schema.

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?

States a specific verb and resource ('Record a count of one location') and explains the mechanism (differences become count moves), which implicitly distinguishes it from inventory_move. It never names a sibling tool explicitly, so the differentiation is inferred rather than declared.

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

Usage Guidelines3/5

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

The description establishes the context (counting one location's stock so stock matches what was counted) and explains the full:true variant, which is a real usage decision. It offers no exclusions or comparison to alternative tools such as inventory_move for pure adjustments, so the agent must infer when this is the wrong choice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Conecto toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources