OffLadder

Start an OffLadder reading

start_my_reading

Read-onlyIdempotent

For someone who doesn't know what to do next, feels stuck or lost about work, or wants help working out a direction, e.g. 'I feel lost in my career', 'I hate my job but don't know what else I'd do', 'help me figure out what to do with my life', 'I'm 35 and still don't know what I want', 'midlife career crisis', 'I just graduated and have no idea what to do'. Returns a link to OffLadder's four quick questions, plus one optional, with their starting world already picked, where OffLadder's coach suggests two directions and a first experiment. Worlds: build (I could build things), nature (I could work with nature), stories (I could tell stories), business (I could solve business problems), people (I could help people), systems (I could understand how things work).

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

Input Schema

Name	Required	Description	Default
`hint`	No	A few words about what they enjoy, used only to pick a world. Not stored.
`world`	No	The world that sounds closest to them, if clear.

Output Schema

Name	Required	Description
`world`	Yes	The starting world picked, if any.
`cta_label`	Yes	A short label for that link.
`start_url`	Yes	OffLadder's short onboarding, with a starting world picked if one was clear.
`continue_url`	Yes	The same link, as the suggested next step.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world behavior, so the description need only add what they don't. It does add meaningful process detail: the starting world is pre-picked, the flow is four quick questions plus one optional, and the output is a link where a coach suggests two directions and a first experiment. It doesn't mention whether the link is persisted or reusable, which is a minor gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead sentence and return description are well front-loaded, but the six-quoted-phrase list and the six world glosses make it long for two optional parameters. The world glosses partly duplicate the enum, and the example phrases, while useful for matching, could be trimmed without losing meaning.

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 only two optional parameters, 100% schema coverage, and an output schema, the description is more than sufficient to invoke correctly. It even describes the return value despite the output schema existing, leaving only minor gaps such as link lifetime or repeat-invocation behavior.

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?

Schema coverage is 100%, so the baseline is 3; the description earns a bump by glossing each world value in plain language ('build (I could build things)', 'systems (I could understand how things work)'), which helps an agent pick an enum value from vague user language. It does not elaborate further on the optional hint parameter beyond what the schema already says.

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 states a concrete action: it delivers a link to OffLadder's four (plus one optional) questions with a starting world already chosen, and describes what the coach then produces (two directions and a first experiment). It is not tautological and is distinguishable from lookup-style siblings, though it never explicitly contrasts itself with explore_career_directions or get_career_direction.

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?

Usage is conveyed strongly through quoted user situations ('I feel lost in my career', 'midlife career crisis', 'I just graduated and have no idea what to do'), which gives an agent concrete trigger conditions. It lacks explicit exclusions or routing to sibling tools for users who already have a direction, so it stops short of full when/when-not guidance.

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

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