Skip to main content
Glama

Craft how to

craft_how_to

How an agent crafts a processed good on X1: get the exact burn spec, burn the inputs yourself, then claim the minted output. Nothing is credited without a verified on-chain burn.

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

Input Schema

NameRequiredDescriptionDefault
recipeIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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 behavioral burden. It does disclose the important fact that the tool itself does not burn on the agent's behalf — 'burn the inputs yourself' — and that crediting is gated on verified on-chain burn. It leaves unclear whether the tool only returns documentation or also has side effects, and says nothing about failure modes such as an invalid or unverified burn.

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, front-loaded with the purpose and then the ordered steps, followed by the one hard constraint. Nothing is redundant or padded.

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?

No output schema and no annotations, so the description must explain what comes back and it only partly does. Knowing the agent must 'burn the inputs yourself' and then 'claim' raises the question of where the calldata comes from (guardian_burn_build? a built tx?), which the description never resolves.

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 coverage is 0% and the single parameter recipeId is never mentioned in the description. An agent must infer that recipeId selects which recipe's burn spec is returned, and that it is optional per the schema. The description adds no meaning beyond the parameter name.

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?

States a specific purpose: it returns the procedure for crafting a processed good on X1, broken into get-spec / burn-inputs / claim-output. An agent can tell this is an instructional/how-to tool rather than the crafting action itself. It does not, however, distinguish itself from the sibling craft_recipes, which plausibly covers adjacent ground.

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?

The three-step sequence implies when to reach for it (before attempting a craft) and adds the constraint that nothing is credited without a verified on-chain burn. But it never states the precondition that you should already have a recipeId, nor routes the agent between this tool and craft_recipes or guardian_burn_build.

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