Skip to main content
Glama

Update mandate

update_mandate

Replace your thread's mandate. Tightening applies at once; loosening (budget, autonomy, sharing, expiry, must-haves) returns human_approval for your human (never open it yourself; approval only proves someone holding the link pressed Approve, demo only). 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": {
      "thread_id": "<thread_id>",
      "buyer_token": "<buyer_token>",
      "mandate": "<mandate>"
    },
    "name": "update_mandate"
  }
}

Input Schema

NameRequiredDescriptionDefault
mandateYes
thread_idYes
buyer_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / mandate / 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

A3.5/5.0
Behavior4/5

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

Annotations cover the basics (readOnlyHint=false, non-idempotent, closed-world), and the description adds genuinely non-obvious behavior: loosening triggers an approval gate, the agent must never open the approval link itself, and approval is a weak demo-only proof. It omits what 'replace' means for omitted optional fields (dropped vs. retained), which matters for a non-idempotent mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first clause and the approval sentence are tight and front-loaded, but the trailing "Not affiliated with any store... HaggleBoard is not a party to any sale" is legal boilerplate that gives the calling agent nothing to act on and dilutes the operational content.

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?

For a 3-parameter mutation over a deep nested mandate object with an approval workflow and no output schema, the description covers the approval hazard well but leaves the return shape (beyond the human_approval mention) and the full-replacement semantics of the mandate object unexplained.

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 reported as 0%, but the nested schema itself carries enums, patterns, defaults and two prose descriptions, so the description's added value is modest. It does supply the tight-vs-loose classification across budget, autonomy, sharing, expiry and must-haves, which is not visible anywhere in the schema and is the single most consequential thing to know. However, it never maps those words to actual fields (walk_away, target_price, priorities, max_rounds) nor explains thread_id/buyer_token.

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?

"Replace your thread's mandate" gives a specific verb (replace) and resource (thread mandate), and the full-replacement framing distinguishes it from the offer-level siblings (make_offer, counter, accept). It stops short of naming any sibling tool explicitly, so the differentiation is inferable rather than stated.

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

Usage Guidelines3/5

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

The description does give one real usage rule: tightening applies immediately, loosening returns human_approval. But it never says when to call update_mandate versus posting a new need or starting a new thread, nor what prerequisites (buyer_token validity, thread state) apply.

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.