Skip to main content
Glama
Sign In

Meridian

by ai.the-meridian
OverviewDiscussions(2)Admin

Get Documentation Page

docs_get
Read-only

Fetches one Meridian public product documentation page in full by relative path (for example mcp-server.mdx, or a nested guides/some-page.mdx). Use after docs_search when you need the whole page. Paths match the meridian://docs/{path} resource index. No app_id. These docs are not app-scoped. Returns path, title, public URL, and markdown/MDX content.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "docs_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesRelative docs path ending in .md or .mdx, as listed by meridian://docs/ or returned by docs_search.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld=false, so the description's added value is the non-app-scoped constraint and the path-to-resource-index relationship, plus the return fields (path, title, URL, content). It doesn't say what happens on a nonexistent path, a minor omission.

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

Conciseness4/5

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

Front-loads the purpose, then usage, scope note, and return shape in a compact paragraph with no filler; the return-field enumeration is slightly verbose but useful.

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 read-only tool with full schema coverage and no output schema, the description covers purpose, sequencing, scope caveat, and return values — nothing an agent needs is missing.

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 coverage is 100%, so baseline is 3; the description earns more by giving concrete path examples (`mcp-server.mdx`, nested `guides/some-page.mdx`) and tying the path format to the `meridian://docs/{path}` index.

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 and resource — fetches one full Meridian documentation page by relative path — and explicitly distinguishes itself from the sibling docs_search (whole page vs. search).

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?

Gives explicit sequencing guidance ('Use after `docs_search` when you need the whole page') and an exclusion ('No `app_id`. These docs are not app-scoped'), which prevents a likely invocation error.

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

All Meridian toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources