Skip to main content
Glama

Show Issuer Agreement

show_agreement

Show the sign-and-approve widget for a draft: the full agreement text, the deal recap (price, cap, total supply, retained/float counts), a legal-name input, an explicit agreement checkbox, then a final confirm card with Mint / Edit setup. Requires the user's Phase token.

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>"
    },
    "name": "show_agreement"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftIdYes
legalNameNo
accessTokenNo
widgetTokenNo
issuerAddressNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden. It does disclose useful behavior: this renders a widget flow ending in a confirm card with Mint / Edit setup, and it requires a Phase token for auth. It does not say whether calling it mutates any server state, what happens on confirm, or whether the displayed recap is read-only.

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

Conciseness3/5

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

It is a single front-loaded sentence with no filler, and the widget-contents enumeration is genuinely informative. But the mid-sentence inventory of UI elements is heavy for one run-on clause and crowds out more decision-relevant information such as parameter roles.

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 a five-parameter tool with no annotations, no output schema, and no documented parameters, the description covers only the purpose and the visual flow. An agent still cannot tell what to pass for draftId versus issuerAddress, or which token parameter is expected, making it insufficient for correct invocation.

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 five parameters, so the description must compensate and largely does not. It never mentions draftId, legalName, accessToken, widgetToken, or issuerAddress by name; "Phase token" ambiguously gestures at one of the two token parameters, and the legal-name mention refers to a UI field rather than the input argument.

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?

"Show the sign-and-approve widget for a draft" gives a concrete verb and resource, and the following clause enumerates what the widget contains (agreement text, deal recap, legal-name input, checkbox, confirm card). It is clearly not the signing action itself, which implicitly separates it from sign_agreement, but it never states that distinction explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"For a draft" plus "Requires the user's Phase token" implies a prerequisite and context, so usage is inferable. However, there is no statement of when to call this instead of sign_agreement or show_coin_setup, and no explicit exclusion of cases where the widget is inappropriate.

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