Skip to main content
Glama

Show coin setup

show_coin_setup

Show the interactive coin-setup widget: name, ticker, category, price, market cap, and ownership split with live supply math. The widget sends the chosen values back to the agent, which creates the draft — the widget itself never mints.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "show_coin_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
tickerNo
categoryNo
priceUsdNo
retainedPctNo
marketCapUsdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful behavior: the widget is interactive, it round-trips values to the agent, and it does not mint. It leaves out what happens on cancel/dismiss, whether it blocks the turn, whether values are prefilled from the parameters, and any permission or state requirements.

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?

Two front-loaded sentences with no filler: field inventory first, then the round-trip semantics and the non-minting guarantee. Slightly dense but every clause carries information an agent needs.

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

Completeness3/5

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

For a widget-rendering tool with six optional parameters, no output schema, and 0% schema coverage, the description covers the core contract but omits return/cancel behavior and parameter prefill semantics. Adequate to call correctly, incomplete for edge cases.

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 0%, so the description must compensate, and it partially does by naming all six underlying fields (name, ticker, category, price, market cap, ownership split). However, it does not explain that the schema properties are seeds/defaults for the widget, nor give formats or constraints for priceUsd, retainedPct, or marketCapUsd.

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 ('Show the interactive coin-setup widget') and enumerates the fields it exposes (name, ticker, category, price, market cap, ownership split). It also draws a clear boundary against minting ('the widget itself never mints'), which implicitly separates it from mint_coin, though no sibling is named 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?

Usage is only implied: the description notes the widget returns chosen values to the agent, which then creates the draft, so an agent can infer it belongs in a pre-mint collection flow. It never states when to prefer this over show_agreement/show_dashboard-style siblings, nor any exclusions or prerequisites.

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