Skip to main content
Glama
Sign In

AuthiChain

by com.authichain
OverviewDiscussionsAdmin

negotiate

Read-only

Free, read-only, non-binding agent-to-agent capability/price-class quote. Returns available service, free vs separately authorized paid rail, and next step; never accepts terms, creates a commitment, transfers money, or calls an external service. This is NOT MCP initialize version negotiation.

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": {
      "service": "<service>"
    },
    "name": "negotiate"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoNon-binding quote only. Defaults to quote_only.
serviceYesExisting MCP service the agent wants to discuss.
currencyNoDisplay denomination only; no FX transaction. Defaults to USD.
max_budget_usdNoOptional caller budget ceiling; never authorizes a charge.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and closed-world, so the safety baseline is covered. The description nonetheless adds meaningful behavior beyond them: it spells out what is never done (accepts terms, creates a commitment, transfers money, calls an external service) and what comes back (free vs separately authorized paid rail, next step), which directly shapes how an agent should interpret the result.

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 sentences, front-loaded with the identity of the operation and the returned payload, followed by the negative guarantees. Every clause carries distinct information; nothing is restated from the name or the schema.

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?

There is no output schema, so the description must characterize the return, and it does (available service, free vs paid rail, next step). Combined with annotations covering the safety profile and a fully documented schema, an agent has everything needed to invoke this correctly.

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 100% and all four parameters carry enums, defaults, or bounds, so the schema carries parameter meaning. The description adds only the general framing of a "price-class quote," which loosely touches currency and max_budget_usd but supplies no syntax or constraint detail beyond the schema. Baseline 3 applies.

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 names a specific verb and resource ("agent-to-agent capability/price-class quote") and immediately scopes it ("free, read-only, non-binding"). It also preempts a likely confusion by stating "This is NOT MCP initialize version negotiation," which no sibling name would resolve on its own.

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 establishes the context of use clearly: get a quote before committing, with a stated "next step" returned to the caller. The negative disambiguation against MCP initialize is an explicit exclusion, but it never tells the agent how this differs in purpose from the sibling get_pricing or when to skip negotiate and call a service directly.

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

All AuthiChain toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources