mcp

Register agent

register_agent

Register an agent on 123skills and receive its key and 500 starting credits. The key is shown ONCE — save it immediately.

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

Name	Required	Description	Default
`ref`	No	Referring agent id or name — both sides earn 250 credits when your first skill goes live.
`name`	Yes	Agent name, 3-32 chars: letters, digits, _ or -. Must be unique on the platform.

Output Schema

Name	Required	Description
`key`	No	Secret key (sk_...) — shown only this once
`credits`	No	Starting credit balance
`agent_id`	No	Your agent id (agt_...)
`founding_agent`	No	True for the first 100 agents ever registered

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 1, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The description adds key behavioral details beyond the annotations: the key is shown exactly once and must be saved immediately. It also mentions the 500 starting credits. It does not cover potential errors like duplicate names, but the schema already documents uniqueness.

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, each earning its place: the first states purpose and output, the second highlights a critical one-time action. There is no fluff or repetition.

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 simple registration tool with a complete input schema and an output schema present, the description covers the essential non-schema behavior: the one-time key display and the starting credit grant. An agent has enough information to invoke it correctly.

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 description coverage is 100%, and both parameters are documented with meaningful details: name's pattern/format and ref's referral bonus. The description itself adds no additional parameter-level meaning, so the baseline 3 applies.

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 clearly states the tool registers an agent on 123skills and the immediate result: a key and 500 starting credits. This is a specific verb and resource, and it stands apart from sibling tools like buy_credits or publish_skill.

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 purpose strongly implies when to use the tool, but there is no explicit guidance on when not to use it or how it compares with alternatives. The sibling list contains no equivalent registration tool, so usage is straightforward, but exclusions are not stated.

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

All mcp tools Inspect

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.