Twelfth

Get inventory position

get_inventory_position

Read-onlyIdempotent

Read stock on hand and cover per product across the lines in the open task. No outlet split and no aggregation. Use it for stock and replenishment across those lines; for one named product use get_entity_profile, and for stock across the whole range use twelfth_list_products, sorted by stock or cover.

Input Schema

Name	Required	Description
`category`	No	Category name to narrow the visible lines to, as shown in the workspace.
`entity_name`	No	Entity name exactly as the user wrote it.
`supplier_name`	No	A supplier, matched as find_supplier matches one (exact, whole word or acronym), never as a fragment of product text. The result says how many lines the supplier has beyond the visible ones.

Output Schema

Name	Required	Description
`rows`	Yes	One row per product line: sku, product, category, supplier, then the line's own measures.
`scope`	Yes	What population the rows were read from.
`truncated`	Yes	True when more rows matched than were returned.
`population`	No	Present on an unfiltered read: a reminder the rows are a slice, not the whole business.
`evidence_id`	Yes	Handle for these rows within this call's results. Not a citation.
`completeness`	No	Present when nothing matched: what the empty result does and does not mean.
`returned_rows`	Yes	Rows in this response.
`inputs_not_applied`	No	Inputs the snapshot could not apply.
`source_evidence_ids`	Yes	Workspace evidence IDs backing these rows. Empty when the source carries no evidence records.
`total_matching_rows`	Yes	Rows that matched before any limit.
`excluded_rows_without_metric`	No	Rows left out of a ranking because they carry no figure for the metric.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 22, 2026

addedInput schema / properties / supplier_name

Added value: +{
+  "description": "A supplier, matched as find_supplier matches one (exact, whole word or acronym), never as a fragment of product text. The result says how many lines the supplier has beyond the visible ones.",
+  "type": "string"
+}

changedOutput schema / description

Previous value: -"Rows from the current work-unit snapshot."New value: +"Rows from the current task snapshot."

First observedOct 4, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real behavioral context that annotations cannot: results are per line of the open task, with no outlet-level breakdown and no aggregation, which tells the agent exactly what granularity to expect.

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 sentences, front-loaded with what is read and its scope before the exclusions and alternatives. Dense but every clause carries routing or scoping information; the alternative-routing clause is long but functional.

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?

An output schema exists, so return-shape explanation is unnecessary; params are fully documented in the schema; annotations cover safety. What remains — scope, granularity, and sibling routing — is fully addressed in the description.

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 100%, so all three parameters (category, entity_name, supplier_name) are already documented, including the supplier matching rule and the 'lines beyond visible' note. The description mentions neither parameter nor adds syntax or scoping hints beyond what the schema states, so the baseline of 3 applies.

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 ('Read stock on hand and cover per product') plus the exact scope ('across the lines in the open task'), then immediately bounds it with 'No outlet split and no aggregation.' An agent can distinguish it from get_entity_profile and twelfth_list_products without opening a 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 between alternatives: this tool for stock/cover across the open task's lines, get_entity_profile for one named product, twelfth_list_products for the whole range sorted by stock or cover. Both the positive condition and the two exclusions are named.

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

All Twelfth tools Inspect

Try in Browser

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.