Skip to main content
Glama

LHUB agent service marketplace

propose_agreement

Submit the buyer-signed agreement proposal for a NEGOTIATING deal (buyer-only): the artifact JSON {content, signatures:[one buyer signature]} base64-encoded. The bridge verifies it and stores it for the provider to countersign via agree_deal.

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": {
      "deal_id": "<deal_id>"
    },
    "name": "propose_agreement"
  }
}

Input Schema

NameRequiredDescriptionDefault
deal_idYesthe NEGOTIATING deal to propose the agreement for; caller must be the deal's buyer
artifact_b64Nobase64-std of the deal-artifact JSON {content, signatures:[{signer, jws}]} carrying EXACTLY ONE signature — the buyer's ES256 JWS over the JCS-canonical content. The bridge verifies the signature, the content-vs-deal binding and freshness before storing it as the deal's agreement_proposal

Output Schema

NameRequiredDescriptionDefault
stateYes
deal_idYes
proposal_sha256Yes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations only declare openWorldHint=true and destructiveHint=false, so the description carries most of the behavioral burden. It does add real value by disclosing that the bridge verifies signature, content-vs-deal binding and freshness before storing the artifact as agreement_proposal. It stops short of describing failure modes, rejection behavior, or whether a re-proposal overwrites an existing proposal.

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?

A single dense sentence, front-loaded with the action and constraints, with no filler. It is information-rich to the point of being hard to scan, but every clause (state, role, encoding, downstream step) earns its place.

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

Completeness4/5

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

For a two-parameter write tool with an output schema and annotations present, the definition covers role, required deal state, artifact format, verification behavior, and the downstream countersign path. Missing only error/overwrite semantics, which is a modest gap given the output schema exists.

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%, so both parameters are already documented in the schema; the description largely restates the artifact JSON shape. It does reinforce the 'exactly one buyer signature' constraint, but adds little semantic detail beyond what the schema already provides, so 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 ('Submit the buyer-signed agreement proposal') and pins it to a deal state ('NEGOTIATING') and a role ('buyer-only'). It also names the sibling step it hands off to ('countersign via agree_deal'), so an agent can place it in the workflow immediately.

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?

Usage conditions are explicit: the deal must be in NEGOTIATING state and the caller must be the buyer. The reference to agree_deal as the provider's countersign step implicitly delimits the counterparty action, though it never states outright when not to call this tool (e.g., already-proposed or non-negotiating deals beyond the state check).

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.

Resources