Assistant tool
coprsetr_get_guide
Fetches one Coprsetr guide by slug as a roadmap: who it applies to, the outcome, timeline, each step with owner and deliverables, and sources.
Updated November 17, 2026
- Website
- OneLifeVibe hub
- Class
- Read · no account needed
- Returns
slug, title, name, type, topic, region, issuer, summary, applies, outcome, timeline, nuance, reviewed, steps[]: title, owner, timing, action, deliverables[]; sources[]: title, url; url
One Coprsetr guide as a step-by-step roadmap (no account needed): who it applies to, the outcome, the timeline, every step with its owner, timing, action and deliverables, and the official sources. Not legal advice or an audit.
Where you can call it
- Account connector https://onelifevibe.com/mcp: served there too, but called with no token or identity, so it never returns account data.
- Free connector https://onelifevibe.com/mcp/free: no sign-in, read-only, rate-limited.
- Switches itself on when coprsetr lists it as an anonymous tool; until then the connectors do not offer it.
Inputs
| Argument | Type | Notes |
|---|---|---|
slug | string matching ^[a-z0-9][a-z0-9-]{1,120}$ | The guide slug from coprsetr_find_guides. |
Example request
POST https://onelifevibe.com/mcp/free
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "coprsetr_get_guide",
"arguments": {
"slug": "<slug>"
}
}
}
Other hub tools
- coprsetr_find_guides find a compliance or security guide
What it does
coprsetr_get_guide returns a single Coprsetr guide laid out as a roadmap. You give it a slug and it hands back who the guide applies to, the outcome it aims at, the timeline, then every step in order. Each step carries its owner, its timing, the action to take and the deliverables that come out of it.
It sits in the Read class, so it changes nothing. No records are created, updated or deleted, and calling it twice with the same slug gives the same answer. No account is needed. A guide is not legal advice and not an audit, so treat it as a plan you read rather than a verdict on someone's setup.
Coprsetr is the front door to the OneLifeVibe network and its developer platform. This tool reads one guide. coprsetr_find_guides is the one that searches.
When an assistant should call it
Call it when someone has picked a guide and wants the whole thing, not a list. The usual moment: coprsetr_find_guides returned a few candidates, the person names one or describes the topic they want, and the assistant needs the steps, owners and deliverables to answer a question or build a checklist.
Skip it for discovery. If you do not have a slug yet, call coprsetr_find_guides first and let the person choose. One guide per call keeps the answer readable, so do not loop through every slug in a result set unless that is what was asked for.
It also fits narrow questions. Ask who owns a step or how long a stage takes, and the owner and timing fields come back per step instead of buried in prose.
Inputs and an example call
One input, required: slug, a string matching ^[a-z0-9][a-z0-9-]{1,120}$. That allows 2 to 121 characters of lowercase letters, digits and hyphens, starting with a letter or digit. Take the value from coprsetr_find_guides and pass it through unchanged.
The free endpoint takes no token. Send a tools/call over JSON-RPC to https://onelifevibe.com/mcp/free with this body: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"coprsetr_get_guide","arguments":{"slug":"<slug>"}}}
The account connector at https://onelifevibe.com/mcp serves the tool too, but calls there carry no token or identity, so it never returns account data. What comes back is the public guide either way.
What comes back
A single guide object. The top-level fields are slug, title, name, type, topic, region, issuer, summary, applies, outcome, timeline, nuance, reviewed, steps, sources and url. applies says who the guide is for, outcome is what finishing it gets you, and timeline is the expected span. nuance holds the caveat that would otherwise get lost, and reviewed carries the guide's review information.
steps is an array. Each entry has title, owner, timing, action and deliverables, and deliverables is itself an array. Use owner and timing for scheduling questions, and action for the what do I actually do answer.
sources is an array of title and url pairs pointing at the official material behind the guide. Show those links when someone wants to check the original. url is the guide's own page on coprsetr.
Errors, limits and safety
The tool is read-only and idempotent, so retries are safe. There is nothing to confirm before calling it and nothing to undo after. It never returns account data, whether you reach it through the free connector or the account connector.
Availability depends on the connector listing it. On coprsetr the tool switches itself on when the site lists it as an anonymous tool. Until then the connectors do not offer it, so check the tool list your client sees before you build a flow around it.
The free connector at https://onelifevibe.com/mcp/free is rate-limited, so a burst of calls can be turned away. Back off and retry rather than hammering it. If a slug does not fit the pattern, fix the slug instead of guessing a variant, and keep the framing honest with your users: a guide is a roadmap, not legal advice and not an audit of their situation.
Questions
Does coprsetr_get_guide need an account?
No. It needs no account and no token, and it is available on the free connector at https://onelifevibe.com/mcp/free, which is read-only and rate-limited. The account connector serves it as well, but calls there carry no identity, so it never returns account data.
Where do I get the slug for coprsetr_get_guide?
From coprsetr_find_guides, the search tool on the same website. Copy the slug exactly as it comes back. It matches ^[a-z0-9][a-z0-9-]{1,120}$, so lowercase letters, digits and hyphens only.
Is the guide legal advice?
No. The guide is a step-by-step roadmap with owners, timing, actions and deliverables, and it is not legal advice or an audit. For anything about money, benefits or health, point the person to the relevant tool on the website.
Build with it. Connect an assistant to https://onelifevibe.com/mcp, or get a free Sandbox key for the Platform API.
Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.