Skip to main content
Glama

Sign Issuer Agreement

sign_agreement

Sign a draft's Issuer Agreement. Widget-only: called from the agreement widget after the user checks the agreement box and types their legal name.

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": {
      "draftId": "<draftId>",
      "legalName": "<legalName>",
      "accepted": "<accepted>"
    },
    "name": "sign_agreement"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
draftIdYes
acceptedYes
legalNameYes
accessTokenNo
widgetTokenNo
idempotencyKeyNo
issuerCategoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals the widget-only precondition but does not state the consequences of signing, whether the action is irreversible, what permissions or tokens are required, or what happens to the draft afterward. For a legal signing mutation, these are material gaps.

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 tight sentences with no filler, and the key purpose and precondition are front-loaded. Every sentence earns its place.

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

Completeness2/5

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

For an 8-parameter, no-annotation, no-output-schema signing tool, the description is too thin. It omits most parameter meanings and does not explain the behavioral consequences of a consequential legal action.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 8 parameters, so the description must compensate. It indirectly accounts for legalName ('types their legal name'), accepted ('checks the agreement box'), and draftId ('a draft's'), but says nothing about accessToken, widgetToken, idempotencyKey, issuerCategory, or title.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: 'Sign a draft's Issuer Agreement.' This clearly distinguishes the action from view-oriented siblings such as show_agreement, though it does not explicitly name an alternative.

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 a strong contextual constraint ('Widget-only') and the exact trigger condition: after the user checks the agreement box and types their legal name. It does not explicitly compare against show_agreement or other alternatives, but the when-to-use context is clear.

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