Skip to main content
Glama

Read section content

read_section
Read-only

Use guide and section IDs to retrieve a section's full stored Markdown content and metadata, including for drafts and finished guides.

Instructions

Return the full stored Markdown content of one section, with guide and section metadata. Works for drafts and finished guides.

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": {
      "guide_id": "<guide_id>",
      "section_id": "<section_id>"
    },
    "name": "read_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
guide_idYesGuide id (g_...).
section_idYesSection id (s_...).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that it returns the complete Markdown body plus metadata and that drafts are readable, which is genuinely useful, but says nothing about size limits, truncation, or error behavior for missing ids.

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?

Two short sentences with the return content front-loaded and the draft/finished scope caveat second. No filler, though 'full stored Markdown content' is slightly redundant in its qualifiers.

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 two-parameter read tool with full schema coverage and no output schema, the description covers what is returned, that metadata accompanies it, and which guide states it works on. An agent could call it correctly; only edge-case behavior is unstated.

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

Parameters3/5

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

Schema coverage is 100% and both parameters carry their own descriptions with id format hints (g_..., s_...). The description only reinforces the one-section scope of section_id; it adds no format or selection semantics beyond the schema, so baseline 3 applies.

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

Purpose4/5

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

States a specific verb and resource: returns the full stored Markdown content of a single section along with guide and section metadata. It is clearly a read operation, implicitly distinct from siblings like edit_section or add_section, though it does not name any of them explicitly.

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

Usage Guidelines3/5

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

The clause 'Works for drafts and finished guides' gives useful applicability context, but there is no explicit when-to-use vs when-to-use-an-alternative guidance, such as pointing to list_guides or next_section for navigation. Usage is only implied.

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