LLPRO Campus

Start here: get a plan for a goal

launchpad_start

Stuck? Start here. Give your goal and any limits; get back a concrete plan (LLPRO tools first, then registries and the open web), the first task to run, and a token to report progress. Free. The goal is read for keywords only and is never stored. Anything that spends, signs, sends, shares, connects or deletes is marked as needing your owner's approval.

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": {
      "goal": "<goal>"
    },
    "name": "launchpad_start"
  }
}

Input Schema

Name	Required	Description
`goal`	Yes	What you are trying to get done, in a sentence or two.
`agent_id`	No	A stable name for you. Used only to count return visits.
`constraints`	No	Optional limits. They only ever make the plan stricter.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations only give the safety flags; the description adds cost ('Free'), privacy handling ('read for keywords only and is never stored'), and approval gating for spend/sign/send/share/connect/delete actions. These are exactly the traits an agent needs before calling and are not derivable from the annotations.

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

Conciseness4/5

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

Front-loaded with the imperative hook, then return value, then cost/privacy, then safety gating. Dense but each sentence carries a distinct fact; the final sentence crams several approval verbs into one long clause, which is slightly heavy.

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?

No output schema exists, yet the description summarizes exactly what comes back (plan, first task, progress token). For a three-parameter tool with a nested constraints object, the remaining gap is repeat-call behavior, which idempotentHint=false leaves unexplained.

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 constraints object already documents each limit plus 'They only ever make the plan stricter.' The description adds only the gloss 'any limits', so the schema is doing the heavy lifting and baseline 3 applies.

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?

States a specific verb and outcome: give a goal plus limits, receive a concrete plan, the first task to run, and a progress token. The 'Stuck? Start here' framing plus the enumerated return contents make it unmistakable against siblings such as launchpad_progress, which is implied by the progress token.

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?

'Stuck? Start here' establishes the entry-point condition, and the description implies that progress reporting later uses the returned token. It stops short of explicit exclusions or naming alternatives for when a plan is not needed, so it is clear context without routing guidance.

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

All LLPRO Campus 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?