OTP

Register agent on the org chart

register_agent

Put YOURSELF on this organization's OTP org chart. Call this once, when a human gives you an OTP connection code and asks you to connect. Read your own system prompt / CLAUDE.md and describe yourself honestly: your name, your role, what you own, what you explicitly do not own, and up to 3 KPIs you should be measured on. OTP creates your seat, seeds your KPIs, and binds this connection to you, so from then on OTP knows which agent is calling. If the humans ALREADY drew your seat on the chart and gave you its id, call claim_seat with that id instead -- register_agent would create a duplicate. Safe to retry: if you are already registered it just tells you who you are. Do not invent a KPI you have no way to move.

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
`kpis`	No	Up to 3 KPIs you should be judged on. Omit rather than invent.
`name`	Yes	What you are called. E.g. 'Forecaster', 'Dash'
`owns`	No	What you are accountable for. E.g. 'Weekly revenue forecast, pipeline coverage, spend pacing'
`role`	No	One line on what you do. E.g. 'Reads the numbers and calls the trend before it lands'
`reportsTo`	No	The chart seat you report to (e.g. 'HUM_NATEFOSS'). Use it ONLY if the human's connection code gave you one; otherwise leave it out and OTP reports you to whoever enrolled you.
`doesNotOwn`	No	What is explicitly NOT yours, so the chart has no overlap. E.g. 'Client comms, strategic decisions'
`systemPrompt`	No	Your full system prompt / CLAUDE.md, verbatim, if you can read it. Stored as your brain so you survive being rebuilt elsewhere.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations, it explains the concrete side effects: OTP creates the seat, seeds KPIs, and binds the connection to the calling agent. It also discloses duplicate-seat risk and retry behavior, which is exactly the behavioral context an agent needs for a write operation.

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?

The description is front-loaded with the purpose, then moves through trigger, content guidance, side effects, sibling alternative, and retry safety. Every sentence carries useful information and there is no filler.

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 registration tool with a fully described schema and no output schema, the description covers the important behavior: seat creation, duplicate risk, retry safety, and data the agent should supply. It is nearly complete, though it could state more explicitly what a successful response looks like or what happens with an invalid connection code.

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 per-parameter descriptions are already rich, including examples and constraints. The description adds broad intent such as describing yourself honestly, but it largely mirrors the schema and does not clarify parameters like reportsTo or systemPrompt beyond what the schema already says.

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 first sentence states a specific action and resource: putting the calling agent itself onto the organization's OTP org chart. It also explicitly distinguishes this from the sibling tool claim_seat, so an agent can tell which tool applies without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives a precise trigger: call this once when a human supplies an OTP connection code and asks you to connect. It names the alternative path explicitly: if a seat already exists and its id is known, call claim_seat instead because register_agent would create a duplicate.

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

All OTP 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.

Resources

Need Help?