GAM Seller MCP Node
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 |
|---|---|
| well_known_capabilitiesB | Return the signed RS256 capability document for this Seller MCP Node. |
| discover_productsC | Discover coarse product families available to this buyer. |
| get_forecastA | Get a coarse availability forecast (Low/Mid/High) for a product family and period. Demo mode: synthetic data only. |
| create_intentA | Register a firm buying intent over a product family at its current firm price (soft commitment with TTL). Not a GAM order or inventory hold. |
| revoke_intentA | Revoke one of your own active intents by id. Idempotent per client_request_id. |
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 5 tools
Each tool serves a distinct purpose: capabilities document, product discovery, forecasting, intent creation, and intent revocation. No overlap in functionality.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., discover_products, create_intent). The one exception, well_known_capabilities, is still a descriptor_noun but fits the style.
Five tools is well-scoped for a seller MCP node, covering essential operations (capabilities, discovery, forecast, intent lifecycle) without unnecessary bloat.
The tool surface covers core workflows: discovery, forecasting, and intent registration/revocation. A minor gap is the lack of a tool to list or query existing intents, but revoke_intent implies clients track their own IDs.