getDocs

Sasha usage guide

How to work with this Sasha instance: knowledge layout, paging, limits, and the playbook for composing with Bernard. Call with no arguments for the table of contents, then once per section you need. Read this before non-trivial work.

Arguments

Argument	Type	Required	Description
`section`	string	optional	Section slug from the table of contents

Scopes

None. Any authenticated connection can call it.

Annotations

Read only: yes
Destructive: no

When to use

Call getDocs before non-trivial work, and when a tool you expect is not in your tool list. It needs no scope. Any authenticated connection can call it.

With no arguments, it returns the table of contents as text.
With section, it returns that section as text. The sections are overview, knowledge, writing, apps-authoring, permissions, skills, working-with-bernard, limits, improvements and what-sasha-can-do.
permissions explains which scope each tool needs and how a person gets a wider grant.
what-sasha-can-do lists recipes for common jobs. It is built from the instance's help index.
improvements ends with a table of recent suggestions. A member sees only the suggestions from this connection. Admin and staff see every suggestion on the instance.

The result is Markdown text, not JSON.

Example

{}

Sasha MCP guide. Call getDocs with a section slug for detail:
- overview: What Sasha is and how to work with it
- knowledge: The knowledge base
- writing: Creating and editing documents
- apps-authoring: Editing the source of a Sasha App
- permissions: What this connection is allowed to do
- skills: Running skills
- working-with-bernard: Working alongside Bernard (website editing)
- limits: Limits and behaviour
- improvements: Suggesting improvements, and what happens next
- what-sasha-can-do: Recipes for common jobs, by family

Then read one section:

{ "section": "limits" }

Refusals and what to do

Error in getDocs: Unknown section "<section>". Call getDocs with no arguments for the table of contents.: the slug is not in the table of contents. Call getDocs with no arguments and use a slug from the list.
If the help index cannot be read, what-sasha-can-do returns a short message that says the recipe list is not available. The other sections still work.

listProjects starts the core loop that the overview section describes.
suggestImprovement and checkSuggestion are described in the improvements section.
checkExecution and the skill family are described in the skills section.
The member-home-write family is described in the writing section.