Skip to main content
Glama

counter_offer

Submit a counter-offer during a negotiation to adjust the price between the seller's last offer and the original listed price.

Instructions

Send a counter-offer in an ongoing negotiation. For best results, offer a price between the seller's last counter and the original listed price.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYesThe negotiation session ID from start_negotiation
priceYesYour counter-offer price in major currency units
currencyNoCurrency code (default: GBP)GBP
Behavior3/5

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

Describes the action and gives a price suggestion, but does not disclose effects on negotiation state or return value. Since no annotations are provided, more behavioral context would be helpful.

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

Conciseness5/5

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

Two concise sentences with no wasted words; front-loaded with the key action.

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?

Covers the basic action but omits information about return values or state changes; adequate but could be more complete given the absence of an output schema.

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?

Adds strategic guidance for the price parameter beyond the schema description, which is valuable for correct usage.

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?

Clearly states the verb 'send' and the resource 'counter-offer in an ongoing negotiation'. Distinguishes well from siblings like accept_deal and start_negotiation.

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?

Provides context for when to use ('in an ongoing negotiation') and offers a best-practice price range, but does not explicitly state when not to use or mention alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/globallayer/merka2a-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server