Twelfth

Get product master

get_product_master

Read-onlyIdempotent

Read price, cost, margin and lifecycle fields for the lines in the open task, filtered by name, category or supplier (filters combine with AND). Use it for product details on those lines; for sales use get_sales_metrics, for stock get_inventory_position, and for every measure on one named product get_entity_profile. A product not found here may still be stocked, so check search_catalogue before saying it is not.

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

changedInput schema / properties / supplier_name / description

Previous value: -"Supplier name to narrow the visible lines to."New value: +"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."

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.5/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the bar is lower, yet the description still adds real behavior: results are limited to lines in the open task, filters combine with AND, and a not-found result is not proof the product is unstocked. Only missing piece is anything about result size or visibility beyond the supplier count note.

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?

Front-loaded with the payload (which fields) and scope (open task lines) in the first clause, then routing, then the caveat. Every sentence carries distinct information; nothing is repeated from the schema or annotations.

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?

Output schema exists so return values need no explanation, annotations cover safety, and the description supplies the scoping constraint, filter semantics, routing alternatives and the false-negative caveat. Nothing an agent needs to invoke it correctly is absent.

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 coverage is 100%, so category, entity_name and supplier_name are already documented, including the supplier matching rule and the note about lines beyond the visible ones. The description only adds the AND-combination semantics across filters, which is the baseline 3 for full schema coverage.

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?

Specific verb+resource: reads price, cost, margin and lifecycle fields, scoped to 'lines in the open task'. It also explicitly names the siblings covering adjacent data (get_sales_metrics, get_inventory_position, get_entity_profile), so an agent can route 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 Guidelines5/5

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

Gives both when-to-use and when-not-to-use: sales goes to get_sales_metrics, stock to get_inventory_position, all measures on one product to get_entity_profile. It also adds a negative-result rule: check search_catalogue before declaring a product missing, which is exactly the kind of guidance an agent needs.

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.