Tools reference
All nine MCP tools: what each does, its inputs, a real result shape and its errors.
Orvio's server offers nine tools. All are read-only, return the latest release only, and give the same answer for the same request.
Most people never write the arguments. You ask in plain words and your tool chooses the tool and fills them in. This reference is for when you want to know exactly what happens, or you build on the server.
The tools#
Each page below is generated from the server's own tool definitions, so it cannot drift from what the server does.
| Tool | What it does |
|---|---|
search_products | Find products in the Orvio catalog, or list them all. Returns identifiers to use with the other tools. |
get_product | Facts about a product's current release: framework, compatibility as recorded, and the names of its pages and components. |
read_release | Start using a whole release: overview, licence text, the publisher's instructions for agents, and the file tree; optionally every file's contents, page by page. For large releases the CLI or the ZIP is faster. |
list_release_files | The release file tree with sizes and SHA-256 digests. |
read_file | One file from the release, byte-identical to the archive entry, with its SHA-256. Text is returned as UTF-8, anything else as base64. Large text files are read in ranges. |
get_page | A page of the product with the source files it needs (components, imported modules, styles, assets, token sources). When the release has the engine's analysis, closure.basis is 'engine-analysis' and closure.complete says whether nothing was left unresolved; otherwise the files are the ones the release indexes record, and the closure is not complete. |
get_component | A component with the source files it needs (imported modules, styles, assets, token sources). When the release has the engine's analysis, closure.basis is 'engine-analysis' and closure.complete says whether nothing was left unresolved; otherwise the files are the ones the release indexes record, and the closure is not complete. |
read_tokens | The product's design tokens as extracted, and the source files that define them. The source files are authoritative. |
list_bookmarks | Products the account saved on the website (read-only). |
How a call works#
- Your tool calls
tools/listto learn the nine tools and their inputs. - It calls
tools/callwith a tool name and arguments. - The result carries the data as structured content, and also as text. The first line is a short summary.
Every result also carries warnings. Usually it is empty. See Membership and access for the two warnings.
Good to know#
- Identifiers name a product, a page, a component or a token. See Identifiers.
- Lists are paged. See Limits and pagination.
- Errors have a stable code and one next step. See Errors and fixes.
- Files are byte for byte the publisher's, with a SHA-256.
read_filereturns text as UTF-8 and anything else as base64.
Was this page clear? Yes · Not reallyEdit suggestions: support@orvio.design