commerce-evidence-toolkit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| review_product_recordB | Review one supplied product record using a selected canonical-field subset and positive USD prices. Optional mapping transforms only explicit supplied fields. Missing or conflicting facts remain on hold. Does not fetch URLs, verify GTIN assignment, or validate a complete provider upload. |
| compare_feed_snapshotsA | Compare supplied source and feed snapshots for exact item IDs, current USD prices, sale state and availability. Requires schemaVersion 1.0, profile openai-native-stable, explicit asOf, maxAgeHours, capturedAt and evidenceRef. Unresolved evidence yields hold with no proposed changes. No fetches or feed writes. See examples/feed-snapshots.json. |
| compare_dimensionsA | Compare supplied length, width and height using exact decimal unit conversion. Input requires schemaVersion 1.0, source and candidate with itemId, basis product/package, evidenceRef, and each axis as {value: decimal string, unit: mm/cm/m/in}; toleranceMm is an explicit decimal string. Same item, basis and named axes required. Unknowns yield hold. Does not establish physical fit or source truth. See examples/dimensions.json. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a clearly distinct evidence operation: single-record review, dimensional comparison, and feed snapshot comparison. Any apparent overlap around USD prices is resolved by the object of comparison (one record vs. source/feed snapshots).
All tools follow a consistent lowercase snake_case verb_noun pattern: review_*, compare_*. The repeated compare_ prefix is justified because the objects differ, and there are no mixed conventions or vague action names.
Three tools is a tight but appropriate scope for a specialized evidence-validation toolkit. Each tool handles a distinct evidence type and earns its place, with no redundant or filler tools present.
Core evidence workflows are covered: canonical product-record review, dimensional comparison, and feed snapshot comparison. However, the toolkit explicitly omits external evidence operations such as URL fetching, GTIN verification, and provider upload validation, which would be minor gaps for some commerce evidence tasks.