Skip to main content
Glama

onboard

Initializes each new session by returning the vault constitution, placement guide, tool list, and current graph state so you can orient before working.

Instructions

Start every new session here. Returns the vault's constitution, its guide to where things go, a short list of the tools, and the state of the graph.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the full behavioral burden. It discloses the four content blocks returned, which is the key behavioral trait of a bootstrap tool, but says nothing about whether the call is free of side effects, how large the response is, or whether it needs to be re-run within a session — gaps that matter for a tool explicitly framed as a session opener.

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 tight sentences with the imperative call to action front-loaded and the return contents enumerated afterward. There is no filler, hedging, or repetition.

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?

With no parameters, no annotations, and no output schema, the description is the only specification, and it accounts for what the agent gets back by listing the four returned components. It is close to sufficient; the remaining omission is any hint of response size or format for what sounds like a large, multi-document payload.

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?

The tool takes zero parameters, so there is no parameter meaning to convey and the baseline of 4 applies. The description does not waste words inventing parameter-like options.

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 names the concrete payload the tool returns — the vault's constitution, a placement guide, a short tool list, and graph state — which is far more specific than restating the name 'onboard'. It does not explicitly contrast itself with potentially overlapping siblings such as context_bundle, librarian_status, or graph_stats, so an agent must infer that this is the broad entry point rather than the narrow 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?

'Start every new session here' is an explicit, unambiguous trigger condition that tells the agent exactly when to reach for this tool. It stops short of saying when not to use it or naming an alternative for partial-orientation needs, which is why it falls short of a 5.

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