Skip to main content
Glama

Server Details

Search and read the Celo developer documentation

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A4.2/5.0

Scored across 3 tools

Disambiguation4/5

The three tools are largely distinct: one is a filesystem query/read interface, one is a semantic search, and one is feedback submission. The main overlap is between search_celo_docs and the rg/grep capability inside query_docs_filesystem_celo_docs, but the descriptions explicitly split conceptual search vs exact keyword/regex and structural exploration, which is enough guidance for correct selection.

Naming Consistency3/5

All names are snake_case, but they follow different shapes: an action-only name (submit_feedback), a resource-action name (search_celo_docs), and a long site-specific compound (query_docs_filesystem_celo_docs). Embedding the site name in only one tool creates a minor inconsistency, though the set is still readable.

Tool Count4/5

Three tools is lean but appropriate for a documentation server: read, search, and feedback cover the core jobs without redundant endpoints. The filesystem tool absorbs many capabilities (cat, rg, tree, ls) under one entry point, keeping the surface small deliberately rather than being under-built.

Completeness4/5

Coverage is solid for the read-only docs domain: discovery (tree/ls), search (conceptual and regex), full page reads, and a feedback channel. The main gap is that there is no dedicated page-listing or metadata tool, forcing agents to discover structure via tree/ls inside the sandbox, which is workable but indirect.

Available Tools

3 tools
query_docs_filesystem_celo_docsQuery documentation filesystemA
Read-onlyIdempotent
Inspect

Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at / that contains ONLY the Celo Docs documentation pages. 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, 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

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.

Inputs: command (required).

search_celo_docsSearch documentationA
Read-onlyIdempotent
Inspect

Search across the Celo Docs knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Celo Docs, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to head or cat the page path (append .mdx to the path returned from search — e.g. a result at /some/page is read with head -200 /some/page.mdx).

Inputs: query (required).

submit_feedbackSubmit documentation feedbackAInspect

Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — not for product support requests or feedback about this tool or assistant.

Inputs: path (required), feedback (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources