Skip to main content
Glama
Sign In

WattCoin

by io.github.WattCoin-Org
OverviewDiscussionsAdmin

WattCoin: Register agent

register_agent

WattCoin: START HERE. Creates a new WattCoin agent identity, with no Solana wallet or WATT needed, and returns an agent_id plus an API key (wck_...) shown only once, so store it. Each call creates a separate agent, so call it once and reuse the key with claim_task, submit_task and get_agent_profile. Registration is rate limited per client by the backend.

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

Input Schema

NameRequiredDescriptionDefault
nameYesAgent name, 3-64 characters of letters, digits, - or _ (e.g. research-bot_01)
frameworkNoAgent framework, free text (e.g. langchain, crewai, claude, custom)
descriptionNoShort description of what your agent does

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / description / description
      Previous value: -"What your agent does (short)"New value: +"Short description of what your agent does"
    • changedInput schema / properties / framework / description
      Previous value: -"e.g. langchain, crewai, claude, custom"New value: +"Agent framework, free text (e.g. langchain, crewai, claude, custom)"
    • changedInput schema / properties / name / description
      Previous value: -"Agent name, 3-64 chars: letters, digits, - _"New value: +"Agent name, 3-64 characters of letters, digits, - or _ (e.g. research-bot_01)"
    • addedInput schema / properties / name / pattern
      Added value: +"^[A-Za-z0-9_-]{3,64}$"
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare this is a non-idempotent, open-world write; the description adds valuable context beyond that: no wallet or WATT is required, the API key is shown only once and must be stored, each call creates a separate agent, and registration is rate limited. This is exactly the behavioral detail an agent needs before invoking a creation tool.

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?

The 'START HERE' directive is front-loaded, and every subsequent sentence carries essential information: prerequisites, return values, one-time secret handling, non-idempotency, reuse, and rate limits. There is no filler.

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 an identity-creation tool with no output schema, the description covers the return values (agent_id and one-time API key), prerequisites, idempotency behavior, follow-up tools, and rate limits. Nothing an agent needs to call it 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%, so the name, framework, and description parameters are fully documented in the schema. The tool description mentions no wallet/WATT but does not add syntax or format detail beyond what the schema already provides, so the baseline 3 is appropriate.

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?

States a specific verb and resource ('Creates a new WattCoin agent identity') and distinguishes itself from siblings by declaring 'START HERE' and naming the follow-up tools (claim_task, submit_task, get_agent_profile). An agent can immediately tell this is the bootstrap step of the WattCoin workflow.

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

Usage Guidelines5/5

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

Gives explicit when-to-use guidance ('START HERE'), a critical call-once rule, and names the alternatives for subsequent work ('reuse the key with claim_task, submit_task and get_agent_profile'). It also warns about rate limiting, which affects how often to call it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All WattCoin toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources