Skip to main content
Glama

navigate_content

Read-only

Navigates retained Markdown content by headings or case-insensitive literal search, returning matches with context so agents can locate paper sections without refetching.

Instructions

Navigate retained Markdown headings or case-insensitive literal matches. Ranges use original Unicode code points for read_content; never refetches.

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": {
      "content_id": "<content_id>"
    },
    "name": "navigate_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoheadings
queryNo
offsetNo
content_idYes
max_resultsNo
context_charsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv7.6.2

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description does add non-obvious behavior: that no refetch occurs and that ranges are expressed in the original Unicode code-point frame of read_content. It does not explain mode-default behavior, result shape, or what happens when a query is absent.

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 dense sentences with no filler, and the core capability is front-loaded. The second sentence is somewhat compressed to the point of obscurity, but nothing is wasted.

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

Completeness2/5

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

With six parameters, zero schema descriptions, and no output schema, the definition should explain how mode and query interact and what navigation results look like. It does neither, leaving key invocation decisions to inference.

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

Parameters2/5

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

Schema description coverage is 0% across six parameters, so the description carries the full burden. It clarifies only the offset/range coordinate frame and indirectly the mode enum; query, max_results, context_chars, and content_id are left entirely unexplained, so the agent gets little beyond the JSON schema's bare types and defaults.

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

Purpose3/5

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

The description names a verb ("Navigate") and two operating modes (headings, case-insensitive literal matches), which gives a rough idea of what the tool does. However, the resource is only vaguely indicated as "retained Markdown", and the agent must infer that navigation happens over content previously obtained via read_content rather than over a live document.

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 phrase "never refetches" and the reference to read_content hint that this tool is a follow-up to a content read, implying you should navigate rather than re-fetch. There is no explicit when-to-use versus when-not-to-use statement and no named alternative among siblings such as read_content or batch_fetch, so guidance remains implied.

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