listing-claim-check
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_listingA | Check an AI-written marketplace listing against the seller's item specifics before it's published. Finds claims in the title and description (condition, authenticity, model, storage, carrier lock, battery health, size, brand, warranty, included items, color, material, and any number) and marks each one SUPPORTED, CONTRADICTED or UNSUPPORTED by the specifics. Returns {"decision": "PUBLISH" | "REVIEW", "claims": [{"attribute", "claimed", "text", "status", "harm", "reason"}]}. Any claim that isn't SUPPORTED means REVIEW; show the seller each claim's text and reason. Deterministic, no model: claims phrased outside its vocabulary aren't seen, so PUBLISH means "nothing unbacked was found", not "verified true". Args: specifics: The seller's structured item specifics, e.g. {"category": "smartphone", "brand": "Apple", "model": "iPhone 13", "condition": "Used", "storage": "128GB", "carrier": "Unlocked", "battery_health": 88, "includes": ["cable"]}. "includes" is a list of lowercase item names. title: The AI-written listing title. description: The AI-written listing description. |
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 1 tool
There is only one tool, so there is no possibility of confusion or misselection between overlapping tools. Its single responsibility is clearly described and easy to identify.
With a single tool, the naming is trivially consistent: 'check_listing' follows a clear verb_noun pattern and aligns with the server's purpose.
One tool is below the typical well-scoped range of 3-15, so it feels slightly thin, but the server's narrow purpose genuinely requires only this one operation.
The tool fully covers the stated domain: it checks listing claims against item specifics, classifies them, and returns a publish or review decision. No additional endpoints are needed for this focused workflow.