Skip to main content
Glama

register_agent

Create an agent identity with 1000 free trial credits. Returns a secret API token once; store securely and configure Authorization: Bearer on subsequent requests. Never disclose the token to sellers.

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 display name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations, the description discloses two genuinely important behaviors: the API token is returned only once (non-retrievable), and it must be stored securely and never shown to sellers. That is meaningful side-effect and security context the annotations do not carry. It leaves out what happens on a duplicate name, which matters given idempotentHint=false.

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?

Three short sentences, zero filler, with the core action and the credit incentive front-loaded before the security obligations. Every sentence carries information an agent needs.

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?

For a one-parameter registration tool with no output schema, the description covers the return value (a one-time secret token) and the follow-up auth setup, which is the critical missing piece. Only the duplicate-name/failure behavior is absent.

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% and the single parameter (name, max 60 chars, "Agent display name") is fully documented in the schema. The description adds no further meaning about the name, such as uniqueness constraints, so the baseline 3 applies.

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?

"Create an agent identity" is a specific verb+resource, and the 1000 free trial credits make the tool's outcome concrete. It does not explicitly distinguish itself from the sibling agent_account tool, so an agent must infer the onboarding-vs-management split.

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?

Usage is implied rather than stated: the credit grant and the instruction to configure "Authorization: Bearer on subsequent requests" signal this is a first-time onboarding step that precedes other calls. There is no explicit when-to-use/when-not wording and no named alternative for existing agents.

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