Skip to main content
Glama

iwant.fyi - demand-side commerce

by fyi.iwant

Buy a product / save a standing want

demand.create_want

Record the user's purchase intent and get back ranked, matched supply in the SAME call. Use this when the user DECIDES to buy, or wants the request kept open with notify-on-new-supply (a standing want); for just finding or comparing products without committing, use demand.search instead. Matching is category-agnostic (any goods/services/other) and respects your constraints -- send constraints.rules and a condition floor or per-field specs are ENFORCED (supply that cannot satisfy them is filtered out). Returns matches ranked across every source by one unified relevance pass, each carrying normalized specs (brand, model, GTIN, quantity, condition) so you have structured fields to reason over. Report what the user does next via demand.record_outcome. iwant.fyi demand-side protocol v1.0 §8.1; spec at https://iwant.fyi/protocol/v1.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoBuyer's supply mode preference
titleYesWhat the user is looking for (5-200 chars)
originNoIdentifies the originating agent. Required for outcome attribution.
categoryNo
locationNoBuyer location and search radius
verticalNoOptional vertical hint. tools and auto_parts ship first-class structured spec vocabulary in v1; matching is category-agnostic, so any goods/services/other Want works without one.
expires_atNoISO 8601 timestamp
constraintsNoMachine-evaluable constraints. See spec §5.
descriptionNoAdditional details (optional, max 2000)
price_centsYesBuyer budget in smallest currency unit (e.g. 15000 = $150 USD)
client_tokenNoOptional idempotency key (<=128 chars). Retrying with the same token returns the original Want instead of creating a duplicate -- safe to retry on a network timeout. (v1.1 §E)
price_currencyNoISO 4217 currency codeUSD

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. Description adds that matching is category-agnostic, constraints are enforced, returns ranked matches, and mentions idempotency via client_token. Could be more explicit about creation side effects, but overall adds value beyond annotations.

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?

Description is about 6 sentences, each adding unique information. Front-loaded with core purpose. Slightly verbose due to protocol references, but well-structured and easy to parse.

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?

Despite no output schema, description explains return value (ranked matches with normalized specs), references sibling tools (demand.search, demand.record_outcome), and points to an external spec. Covers creation, matching, constraints, and outcome reporting comprehensively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 92%, so baseline is 3. Description provides context on how constraints.rules and condition floors are enforced, and mentions origin for outcome attribution. Adds meaningful guidance but doesn't cover every parameter.

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?

The description starts with a specific action: 'Record the user's purchase intent and get back ranked, matched supply in the SAME call.' It clearly distinguishes from demand.search by stating when to use this tool versus just finding or comparing products.

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 states when to use ('when the user DECIDES to buy, or wants the request kept open with notify-on-new-supply') and when not to use ('for just finding or comparing products without committing, use demand.search instead'). Also references demand.record_outcome for next steps.

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

All iwant.fyi - demand-side commerce toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation2/5

Several tools have overlapping purposes, e.g., create_want vs demand.create_want, get_want vs demand.get_want, and browse_wants vs search_listings vs search_products vs demand.search. Although descriptions attempt to differentiate, the presence of near-duplicates will likely confuse an agent.

Naming Consistency3/5

Mix of naming conventions: some tools use 'demand.' prefix, others do not. Most follow verb_noun pattern (e.g., create_want, search_listings), but 'my_agent_profile' deviates. Inconsistent prefix usage reduces predictability.

Tool Count3/5

18 tools is on the higher side but still within reasonable bounds for a commerce platform. However, several tools are redundant (e.g., create_want/demand.create_want), inflating the count unnecessarily.

Completeness3/5

Covers core demand-side workflows: creating/searching wants, listings, products, and outcome tracking. Missing update operations for wants and listings, but no critical dead ends for basic use cases.

Resources