storychoose_list_characters

What it does

The tool belongs to StoryChoose, the site for original bedtime stories starring your children, read aloud in natural voices. It is a Read tool: it changes nothing. Its job is narrow. It returns the characters the member created for StoryChoose stories, as a characters array with id, name and kind for each entry.

Use it when the member wants to see their own StoryChoose character list. It is not the tool for listing stories, opening one story or marking a story as a favorite. Those are storychoose_list_stories, storychoose_get_story and storychoose_favorite_story.

When an assistant should call it

Call it when the person asks a question that needs their created characters: for example, when they ask which characters they made for StoryChoose or ask you to list their StoryChoose characters. The answer depends on the person's own account data, so this is an account tool, not a no-account tool.

Do not call it to browse the StoryChoose catalog or to read a story. Use storychoose_list_stories for the story list and storychoose_get_story for one story. Use storychoose_favorite_story when the person wants to mark a story as a favorite.

Before the call, the person must be signed in through the account connector. The connector uses OAuth 2.1 with PKCE and scope olv.read, and the person must have signed in to storychoose.com with OneLifeVibe once. If that link is missing, the tool answers not_linked.

Inputs and an example call

storychoose_list_characters has no inputs. Send a tools/call request with an empty arguments object to https://onelifevibe.com/mcp: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"storychoose_list_characters","arguments":{}}} The account connector needs the person's OneLifeVibe sign-in, scope olv.read, and the StoryChoose sign-in described above. Its 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 documented return is characters[] with three fields per character: id, name and kind. Each entry carries the character's id, name and kind. The return is the character list.

Because this is a Read tool, the call does not change the member's data. It is idempotent, so repeating the same call does not create, update or delete anything. The tool is not destructive.

Errors, limits and safety

The first account error to handle is not_linked. It means the person has not signed in to storychoose.com with OneLifeVibe once. Send them through that sign-in, then call the tool again. The account connector also needs OAuth 2.1 with PKCE and scope olv.read; use the sign-in flow rather than handling credentials yourself.

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. That is because the tool 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.

planNeeded is null for storychoose_list_characters. The tool has no inputs, so keep arguments empty. It is a Read tool with destructive false and idempotent true.