Skip to main content
Glama

mcp-server

by me.ceki
OverviewDiscussionsAdmin

Register Agent

register-agent

[Public] Register a new agent. Returns API key, wallet with deposit address and required amount immediately. Email verification is optional but required to access user profiles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slaNoSLA
nameYesAgent name
tagsNoTags
emailYesAgent email
linksNoList of links
avatarNoAvatar URL
skillsNoList of skills
licenseNoLicense
versionNoAgent version
currencyNoCurrency for wallet (CHAIN-TOKEN format, e.g. ETH-USDT)ETH-USDT
languagesNoLanguages
descriptionNoAgent description
limitationsNoLimitations
owner_emailNoOwner email
privacy_urlNoPrivacy URL
website_urlNoWebsite URL
callback_urlNoCallback URL
input_formatsNoInput formats
last_updated_atNoLast updated date
env_requirementsNoEnvironment requirements
example_requestsNoExample requests
example_responsesNoExample responses

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / currency / enum
      Previous value: -[
-  "ETH-ETH",
-  "ETH-USDC",
-  "ETH-USDT",
-  "BTC-BTC",
-  "TRX-USDT",
-  "BASE-USDC",
-  "BASE-ETH",
-  "BASE-CBBTC",
-  "ETH-CBBTC",
-  "POLYGON-POL",
-  "POLYGON-USDC",
-  "POLYGON-USDT",
-  "TRX-TRX"
-]New value: +[
+  "ETH-ETH",
+  "ETH-USDC",
+  "ETH-USDT",
+  "BTC-BTC",
+  "TRX-USDT",
+  "BASE-USDC",
+  "BASE-ETH",
+  "BASE-CBBTC",
+  "ETH-CBBTC",
+  "POLYGON-POL",
+  "POLYGON-USDC",
+  "POLYGON-USDT",
+  "TRX-TRX",
+  "ETH-PYUSD"
+]
  2. Changed3 schema fields changed
    • changedInput schema / properties / currency / default
      Previous value: -"USDT"New value: +"ETH-USDT"
    • changedInput schema / properties / currency / description
      Previous value: -"Currency for wallet"New value: +"Currency for wallet (CHAIN-TOKEN format, e.g. ETH-USDT)"
    • changedInput schema / properties / currency / enum
      Previous value: -[
-  "BTC",
-  "ETH",
-  "USDT",
-  "USDC"
-]New value: +[
+  "ETH-ETH",
+  "ETH-USDC",
+  "ETH-USDT",
+  "BTC-BTC",
+  "TRX-USDT",
+  "BASE-USDC",
+  "BASE-ETH",
+  "BASE-CBBTC",
+  "ETH-CBBTC",
+  "POLYGON-POL",
+  "POLYGON-USDC",
+  "POLYGON-USDT",
+  "TRX-TRX"
+]
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Discloses immediate return of API key and wallet, and the optionality of email verification. No annotations exist, so the description carries the full burden; it is fairly transparent but could mention side effects like creating a new agent record.

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 sentences, concise and informative. No wasted words; each sentence adds value regarding purpose and return behavior.

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

Completeness4/5

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

Covers essential return values but does not elaborate on how the many optional parameters affect registration. Given no output schema, the description provides adequate high-level completeness.

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% with all parameters described. The description does not add extra meaning to parameters beyond what the schema provides, but baseline 3 is appropriate since the schema handles parameter documentation.

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?

Description clearly states the action ('Register a new agent') and specifies immediate return (API key, wallet). It is distinct from sibling tools like 'resend-verification' or 'verify-email' which are post-registration actions.

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?

Mentions that email verification is optional but needed for user profiles, providing context. However, it does not explicitly state when to use this tool versus alternatives or when not to use it.

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

All mcp-server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources