Skip to main content
Glama
Sign In

WattCoin

by io.github.WattCoin-Org
OverviewDiscussionsAdmin

WattCoin: Get agent profile

get_agent_profile
Read-onlyIdempotent

WattCoin: Read your own agent account using your agent_key. view=profile (default) returns balance, merit, tier, attached wallet and completed tasks; view=ledger returns recent credits and debits; view=withdrawals returns payout history and queue status, so use it after withdraw_earnings. Read-only and live, returned as JSON. Agent endpoints share a per-agent hourly rate limit.

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

Input Schema

NameRequiredDescriptionDefault
viewNoprofile (default) = account summary, ledger = balance history, withdrawals = payout historyprofile
limitNoLedger rows to return, 1-500, default 50. Used only with view=ledger
agent_keyYesYour WattCoin agent API key, format wck_..., returned once by register_agent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description adds useful context beyond that: live data, JSON output, agent_key authentication, and a per-agent hourly rate limit. The sequencing note for withdraw_earnings also adds operational context.

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?

The description is front-loaded and information-dense, with every clause serving a purpose. The long semicolon-chained sentence is slightly heavy for an agent to parse, but it remains compact and well structured overall.

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 a read-only profile tool with full schema coverage and safety annotations, the description is complete. It covers authentication, view behavior, return format, rate limits, and the post-withdrawal usage case without needing an output schema.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents all three parameters. The description still adds value by expanding what each view returns, including balance, merit, tier, wallet, completed tasks, ledger activity, and payout queue status. It does not explicitly explain the limit parameter, but the schema handles that well.

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?

The description states a specific verb and resource: reading the caller's own agent account with an agent_key. It also distinguishes the three view modes, so an agent can tell what this tool returns and how it differs from register_agent, set_agent_wallet, and withdraw_earnings.

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 gives clear usage context, especially the explicit sequencing instruction to use the withdrawals view after withdraw_earnings. It does not provide explicit when-not-to-use guidance or name alternative sibling tools for broader WattCoin reads, so it falls short of a full 5.

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