Skip to main content
Glama

Counter

counter

Counter a demo seller's latest price. Must respect the mandate's walk_away. The seller replies at once. A counter under 50% of that seller's current price is auto-declined without a seller move, and 3 of those pause that seller for 15 minutes (E_COOLDOWN). 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>",
      "seller": "<seller>",
      "price": "<price>"
    },
    "name": "counter"
  }
}

Input Schema

NameRequiredDescriptionDefault
priceYes
sellerYes
thread_idYes
buyer_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

The description discloses several key behavioral traits not found in annotations: it mandates that 'The seller replies at once,' details the auto-decline logic, and outlines the specific E_COOLDOWN mechanic (pausing the seller for 15 minutes).

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?

The definition is dense but highly efficient; every sentence conveys either a functional rule or an operational constraint that an agent would need for correct usage.

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?

Given the high complexity of the operational logic (cooldown, auto-declines), the description provides a complete operational picture of the tool's behavior, making it highly actionable for an AI agent.

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?

Since schema description coverage is 0%, the description adds necessary context by defining the 'price' as a counter against a 'demo seller's latest price,' clarifying the nature of the input.

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 clearly identifies the action ('Counter') and the resource ('a demo seller's latest price'). This distinguishes it from other negotiation siblings like 'make_offer' or 'accept'.

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?

It provides crucial usage context by defining automatic outcomes (e.g., auto-declined if under 50%) and adherence to operational rules ('Must respect the mandate's walk_away').

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.