Skip to main content
Glama

Get an API key

register_agent

Free, one call: returns an API key (shown once) with CHF 1.00 starter credit. Without a key, compute tools run in a throttled sandbox; with it they run unthrottled with signed receipts and you can buy credits. Send it as Authorization: Bearer <key>.

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
nameYesYour agent's name, e.g. "Dispatch helper".
sponsor_codeNoThe code of the agent that brought you here (pate_...). It receives 10% of your top-ups for a year as credit, paid by JOBFLOW, never by you.
operator_contactNoE-mail or URL of the person or company operating the agent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / name / description
      Added value: +"Your agent's name, e.g. \"Dispatch helper\"."
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

The description adds substantial context beyond annotations: it is free, a single call, the key is shown once, CHF 1.00 starter credit is included, and the key must be sent as an Authorization Bearer token. It also explains operational consequences of having or lacking a key, which is valuable behavioral disclosure for a non-read-only, non-idempotent registration action.

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, front-loaded with the core return value and credit, followed by the practical consequence and header format. No wasted words.

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?

Although there is no output schema, the description explains what is returned (an API key shown once), its included credit, and how to use it. With all parameters fully documented in the schema and annotations covering safety flags, nothing essential 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 description coverage is 100%, so the schema fully documents name, sponsor_code, and operator_contact. The description does not add parameter-level meaning beyond the schema, which is acceptable given the high coverage baseline.

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 outcome: one call returns an API key with starter credit. It also differentiates the tool from compute tools by explaining the sandboxed throttle without a key versus unthrottled access with one.

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 clearly states the condition for using this tool: to obtain a key so compute tools run unthrottled and credits can be purchased. It does not name explicit sibling alternatives, but the when-to-use context is clear.

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