Skip to main content
Glama

Cerebrium Docs

by ai.cerebrium
OverviewDiscussionsAdmin

query_docs_filesystem_cerebrium

Read-onlyIdempotent

Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at / that contains ONLY the Cerebrium documentation pages and OpenAPI specs. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks.

This is how you read documentation pages: there is no separate "get page" tool. To read a page, pass its .mdx path to head or cat — a page at the URL path /some/page lives at /some/page.mdx. To search the docs with exact keyword or regex matches, use rg. To understand the docs structure, use tree or ls.

Paths are specific to this site — never guess them. Discover real paths with tree / -L 2, ls /, or the search tool before reading. If a path does not exist, that only means the guess was wrong; it does NOT mean the topic is undocumented — use rg -il "keyword" / to find where it is covered.

Workflow: Start with the search tool for broad or conceptual queries like "how to authenticate" or "rate limiting". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path.

Supported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run --help on any command for usage.

Each call is STATELESS: the working directory always resets to / and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with && or pass absolute paths (e.g., cd /some-directory && ls or ls /some-directory). Do NOT assume that cd in one call affects the next call.

Examples (replace the placeholder paths with real ones from tree or search):

  • tree / -L 2 — see the top-level directory layout

  • rg -il "rate limit" / — find all files mentioning "rate limit"

  • rg -C 3 "apiKey" /some-directory/ — show matches with 3 lines of context around each hit

  • head -80 /some/page.mdx — read the top 80 lines of a specific page

  • head -80 /page-one.mdx /page-two.mdx /section/page-three.mdx — read multiple pages in one call

  • cat /some/page.mdx — read a full page when you need everything

  • cat '/openapi/https://s3.eu-west-1.amazonaws.com/www.cerebrium.ai/openapi_spec.json' | jq '.paths | keys' — list OpenAPI endpoints

OpenAPI specs for this site are mounted at: '/openapi/https://s3.eu-west-1.amazonaws.com/www.cerebrium.ai/openapi_spec.json', /openapi/package.json, /openapi/data/training-dataset-example.json. Use them to answer questions about endpoints, request/response schemas, parameters, and authentication.

Output is truncated to 30KB per call. Prefer targeted rg -C or head -N over broad cat on large files. To read only the relevant sections of a large file, use rg -C 3 "pattern" /path/file.mdx. Batch multiple file reads into a single head or cat call whenever possible.

When referencing pages in your response to the user, convert filesystem paths to URL paths by removing the .mdx extension. For example, /some/page.mdx becomes /some/page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandYesA shell command to run against the virtualized documentation filesystem (e.g., `rg -il "keyword" /`, `tree / -L 2`, `head -80 /path/file.mdx`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A5/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already state readOnlyHint=true, openWorldHint=false, idempotentHint=true, and destructiveHint=false. The description adds substantial behavioral context beyond that: the filesystem is a sandbox, each call is stateless with the working directory resetting to `/`, output is truncated to 30KB, there are no writes/network/process control, and missing paths only mean the guess was wrong—not that the topic is undocumented. This fully discloses practical behavioral constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Although long, the description is densely packed with necessary information and is well structured: purpose, path rules, workflow, supported commands, statelessness, examples, OpenAPI mounts, output limits, and response formatting. Every sentence earns its place, and the most critical guidance is front-loaded before examples.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter shell-like tool with no output schema, this description is exceptionally complete. It covers how to read pages, how to search, how to handle missing paths, stateless behavior, output truncation, OpenAPI spec locations, and even how to convert paths back to URLs when responding to the user. An agent has everything it needs to invoke and interpret the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single `command` parameter, but the description adds enormous semantic value on top of the schema. It enumerates supported commands, gives concrete examples with placeholders, explains path-to-URL conversion, shows how to chain commands with `&&`, and demonstrates use of the mounted OpenAPI specs with `jq`. The parameter gains far more meaning than the schema alone provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/`' that is explicitly limited to Cerebrium documentation and OpenAPI specs. It clearly distinguishes this tool from the sibling search_cerebrium by framing it as the way to read actual pages, not just search, and even notes there is no separate 'get page' tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides an explicit workflow: 'Start with the search tool for broad or conceptual queries' and 'Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path.' It also warns against guessing paths and tells the agent to use `tree` or `rg` first, covering both when to use and how to use the tool effectively.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Cerebrium Docs toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources