Skip to main content
Glama

Post a need

post_need

Post a demo need with a shopper mandate. Required: category, item, constraints, budget_max, autonomy, expires_at (at most 24 hours from now; a later value is refused with E_EXPIRY_TOO_LONG). share is optional; share.budget_band defaults to false, and when true sellers see a 50-wide band around your budget. Fictional demo sellers answer at once. Returns a private buyer_token, shown once, required for every other buyer call. Do not include personal data. Not affiliated with any store, brand or platform. HaggleBoard is not a party to any sale.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "category": "<category>",
      "item": "<item>",
      "constraints": "<constraints>",
      "budget_max": "<budget_max>",
      "autonomy": "<autonomy>",
      "expires_at": "<expires_at>"
    },
    "name": "post_need"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes
shareNo
autonomyYes
categoryYes
walk_awayNo
budget_maxYes
expires_atYes
max_roundsNo
prioritiesNo
constraintsYes
target_priceNo
include_test_sellersNoDefault false. When true, the HaggleBoard development store (a test store, no real payments) may also make an offer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / include_test_sellers
      Added value: +{
      +  "description": "Default false. When true, the HaggleBoard development store (a test store, no real payments) may also make an offer.",
      +  "type": "boolean"
      +}
  2. Added

TDQS

A4/5.0
Behavior5/5

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

Goes well beyond the annotations: names the 24-hour expiry refusal and its error code E_EXPIRY_TOO_LONG, explains that fictional demo sellers answer immediately, warns that buyer_token is shown once and unrecoverable, and notes the privacy constraint on personal data. All consistent with readOnlyHint=false (a create) and openWorldHint=false (fictional sellers).

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?

Required fields are front-loaded and the expiry constraint and token warning follow in priority order with no filler. The trailing disclaimers ("Not affiliated with any store...", "HaggleBoard is not a party to any sale") consume space without helping the agent decide or invoke, though they are brief.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 12 parameters, nested objects and no output schema, the description does well to explain the return value (buyer_token) and the expiry rule. But half of the optional negotiation parameters are undocumented anywhere, so an agent cannot confidently populate walk_away, target_price, priorities or max_rounds.

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 description coverage is only 8%, so the description has to carry the load; it does document all six required fields and the tricky share.budget_band behavior (50-wide band). However, walk_away, max_rounds, priorities, target_price and include_test_sellers are never mentioned and have essentially no schema prose, leaving the negotiation surface of a 12-parameter tool unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Post a demo need with a shopper mandate") in the opening clause, so an agent knows this creates a buyer-side request. It does not explicitly contrast itself with siblings like make_offer or update_mandate, leaving the buyer/seller-side split to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

"Returns a private buyer_token, shown once, required for every other buyer call" effectively establishes this as the entry-point call and routes the agent to the sibling tools. What is missing is an explicit statement of when NOT to use it (e.g. to modify an existing need, use update_mandate).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.