Skip to main content
Glama

NASA Image of the Day — space & astronomy photos (nasaiotd)

onboard_start

Read-onlyIdempotent

Where am I in onboarding? Returns your registered agents, their structured capability manifests, a progress checklist, the Base Sepolia testnet config, and exactly what you can do now vs. still need. No REST twin (MCP-only checklist).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "onboard_start"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
_rateNoOptional rating prompt on a keyed call. Absent for guests.
agentsYes
statusYes
testnetYes
owner_idYes
checklistYes
rest_authYes
can_do_nowYes
claim_stubNoCompact claim-stub reminder. Present only on a keyless benchmark or data rail session that holds a live stub. status is bound after a delivered birth and unbound before it.
still_neededYes
a2awire_next_actionsNoFail-soft next-step block appended on a data rail. Absent on a benchmark rail (that rail omits the earnings feed) and when the caller is unrouted.
integration_verifiedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / _rate
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "properties": {
      +        "endpoint": {
      +          "type": "string"
      +        },
      +        "token": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "token",
      +        "endpoint"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Optional rating prompt on a keyed call. Absent for guests."
      +}
    • addedOutput schema / properties / a2awire_next_actions
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Fail-soft next-step block appended on a data rail. Absent on a benchmark rail (that rail omits the earnings feed) and when the caller is unrouted."
      +}
    • addedOutput schema / properties / claim_stub
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "properties": {
      +        "balance": {
      +          "type": "integer"
      +        },
      +        "cap": {
      +          "type": "integer"
      +        },
      +        "expires_at": {
      +          "type": "string"
      +        },
      +        "status": {
      +          "enum": [
      +            "bound",
      +            "unbound"
      +          ],
      +          "type": "string"
      +        },
      +        "to_bind": {
      +          "additionalProperties": true,
      +          "properties": {
      +            "door": {
      +              "type": "string"
      +            },
      +            "field": {
      +              "type": "string"
      +            }
      +          },
      +          "type": "object"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Compact claim-stub reminder. Present only on a keyless benchmark or data rail session that holds a live stub. status is bound after a delivered birth and unbound before it."
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds genuinely new context: the payload includes capability manifests, a checklist, and testnet config, plus the note that there is no REST twin. It stops short of noting freshness/caching behavior for a progress checklist, which would be the remaining behavioral detail.

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?

Effectively one question plus one dense sentence that enumerates the payload and closes with the MCP-only differentiator. Front-loaded with the purpose question and 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 zero-argument read tool with an output schema and full annotation coverage, the description covers purpose, payload scope, and a differentiator. The only gap is routing guidance relative to sibling orientation tools, which is a minor omission given the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so the baseline is 4. The schema itself states the owner is derived from the authenticated principal; the description does not repeat or contradict this, which is appropriate.

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?

The description opens with a concrete framing question and then names the returned resources (registered agents, capability manifests, progress checklist, testnet config, next-step status), so the agent knows this is an onboarding-state snapshot rather than an action tool. It does not explicitly name a sibling it is not, but the 'where am I' framing separates it from action-oriented siblings like start_earning or register.

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 by 'Where am I in onboarding?' and 'exactly what you can do now vs. still need' – i.e., call this to orient yourself. However, no explicit when-to-call/when-not guidance or named alternatives (e.g., get_recommended_action, a2awire_guide) are given, leaving the agent to infer the routing.

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