storychoose_get_story

What it does

StoryChoose at storychoose.com writes original bedtime stories starring your children, read aloud in natural voices. storychoose_get_story returns the full text of one of those stories, chapter by chapter, so an assistant can read it back or work through it in order.

It is a Read tool: it changes nothing. Call it to fetch text that already exists. It does not draft, rewrite or save a story, and one call covers one story.

When an assistant should call it

Call it after storychoose_list_stories has given you a story_id, when the person wants the story itself: read me chapter two, what happens at the end, or find the part about the lighthouse.

If they are still choosing between stories, list first and fetch only the one they pick. The call is idempotent, so fetching the same story again is harmless when a conversation reconnects or a client retries.

For the people in a story, use storychoose_list_characters. Marking a story as a favorite is storychoose_favorite_story, which does change something.

Inputs and an example call

One input: story_id, required, a string of up to 80 characters, taken from storychoose_list_stories. Send it exactly as returned.

Send the call to https://onelifevibe.com/mcp as JSON-RPC 2.0: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"storychoose_get_story","arguments":{"story_id":"the id from storychoose_list_stories"}}}

The account connector at that endpoint needs the person's OneLifeVibe sign-in (OAuth 2.1 with PKCE) and the scope olv.read, and the person must have signed in to storychoose.com with OneLifeVibe once. That sign-in is set up for Meta Muse today (client onelifevibe-muse); other MCP clients reach the no-account tools through the free connector.

What comes back

The result carries id, title, language, and chapters, an array where each entry has a title and text. Text is the body of that chapter; walk the array in order to read the whole story.

Because the full text arrives in one response, a long story makes a long reply. If the person wants a single chapter, use the chapter titles to pick the entry before quoting anything.

The tool writes nothing back: no chapter is marked as read and no favorite is added. Calling it again with the same story_id returns the same structure.

Errors, limits and safety

If the person has never signed in to storychoose.com with OneLifeVibe, the account connector answers not_linked. Ask them to sign in there once with OneLifeVibe, then repeat the call.

On the Platform API the tool is listed in GET /api/platform/v1/tools, but a platform key gets 501 world_tools_unavailable for it today, because it acts on one member's own data. A platform key can call the world catalogue, the tool registry, the network directory tool and the event log. For this tool, use the account connector.

It is a Read tool and destructive is false, so retrying after a dropped connection is safe.