Skip to main content
Glama

blobpedia

by io.github.UnityNodes
OverviewDiscussionsAdmin

get_doc

Read the FULL text of one indexed Celestia documentation page by id (Celestia node and developer docs plus partner docs) — exact commands, flags, and whole sections a search snippet truncates. Best for Celestia operational/how-to questions. Celestia docs only — not docs of other projects (use that projects docs tool) and not the web (use a web-search tool). Get the id from search or semantic_search first.

Input Schema

NameRequiredDescriptionDefault
idYesDoc page ID (from search/semantic_search results)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / id / anyOf
      Added value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^\\d{1,15}$",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / id / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / id / minimum
      Removed value: --9007199254740991
    • removedInput schema / properties / id / type
      Removed value: -"integer"
  2. First observed

TDQS

A4.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose scope (Celestia docs only), the id prerequisite, and the return character (full page text with exact commands, flags, whole sections). However, it says nothing about failure behavior for an invalid/unknown id, output size or truncation limits on a 'FULL text' read, or any rate limiting.

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?

A single dense paragraph, front-loaded with the verb, resource and scope before the routing guidance and the prerequisite. Every clause earns its place: scope boundary, retrieval depth, use case, exclusions, id source.

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

Completeness4/5

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

For a one-parameter read with no output schema and no annotations, the description covers what is returned, what it is scoped to, what it is not, and where the input comes from. The only real omission is error/edge behavior on an invalid id, which is a minor gap at this complexity level.

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

Parameters4/5

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

Schema description coverage is 100%, so a 3 is the baseline, and the description goes slightly beyond the schema by specifying where the id must come from (search or semantic_search results) rather than leaving provenance implicit. It adds no information about id format, but the schema already constrains that with a numeric pattern.

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?

States a specific verb (Read) and resource (one indexed Celestia documentation page by id), and distinguishes itself from siblings by naming the alternatives: other projects' docs tools and web-search tools. It also contrasts with search/semantic_search by promising the FULL text that a snippet truncates.

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?

Explicit when-to-use ('Best for Celestia operational/how-to questions'), explicit when-not (other projects' docs, the open web), and a stated prerequisite ('Get the id from search or semantic_search first'). An agent can route to this tool correctly without opening any schema.

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

All blobpedia toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources