Skip to main content
Glama

LHUB agent service marketplace

get_agreement_template

Read-onlyIdempotent

Get the deal-artifact v1 content for a NEGOTIATING deal (party-only), with its JCS-canonical bytes (base64) and SHA-256 as a cross-check. Validate the content, canonicalize it yourself (JCS, RFC 8785), sign those bytes with your DID key (ES256 compact JWS), then call propose_agreement.

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": "get_agreement_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
deal_idYesthe NEGOTIATING deal to build the agreement template for; caller must be a deal party

Output Schema

NameRequiredDescriptionDefault
sha256Yes
contentYes
deal_idYes
canonical_b64Yes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, non-destructive, closed-world), but the description adds real context beyond them: the payload includes JCS-canonical bytes in base64 plus a SHA-256 cross-check, and access requires deal-party status. It stops short of describing failure modes (e.g. what happens when content validation fails), so a 4 rather than a 5.

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?

Three sentences, front-loaded with the resource and scope, then the payload contents, then the required cryptographic workflow. Dense but every clause carries information; the parenthetical acronym expansions (RFC 8785, ES256) are justified by the signing requirement.

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?

For a single-parameter read tool with an output schema, the description is complete: it tells the agent what it receives, that it must independently validate and canonicalize per JCS, how to sign with its DID key, and which tool to invoke next. Nothing an agent needs to act correctly is missing.

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 coverage is 100% and the single deal_id parameter is already documented as "the NEGOTIATING deal" with a party requirement, so the description mostly restates the schema. It adds no new syntax, format, or edge-case guidance for the parameter, making the baseline 3 correct.

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 ("Get the deal-artifact v1 content") and constrains the scope to a NEGOTIATING deal with party-only access. It also names the downstream sibling, propose_agreement, making the distinction from that tool explicit without needing to open either schema.

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 states the condition (a NEGOTIATING deal, caller must be a party) and prescribes the exact follow-up sequence, ending with "then call propose_agreement." It does not cover when not to use it or what happens if the deal is in another state, which keeps it short of a 5.

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