Skip to main content
Glama

owa_help_page

Retrieve the full knowledge document for an owa_help_search result ID, giving you the step-by-step instructions behind the excerpt.

Instructions

Read one knowledge document by the id an owa_help_search hit carries (e.g. "W-11", or "internal:memory/....md") -- the steps behind the excerpt.

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": {
      "id": "<id>"
    },
    "name": "owa_help_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
partNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden. 'Read' implies a safe read-only operation and the id examples ('W-11', 'internal:memory/....md') hint at the id namespace, but nothing is said about behavior for unknown ids, whether the whole document or a fragment is returned, or what the second parameter controls.

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 front-loaded sentence with the key constraint (id comes from a search hit) and useful examples, with no filler. Every clause adds information.

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 simple read-by-id tool with no output schema, the description covers what is returned ('the steps behind the excerpt') and how to obtain the id. The one missing piece is the 'part' parameter, which is undocumented everywhere.

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 0% across two parameters. The description meaningfully documents 'id' — its origin (a search hit) and two concrete formats — but 'part' is left entirely unexplained in both schema and description, leaving a real gap for a numeric parameter whose semantics are non-obvious.

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 ('Read one knowledge document by the id') and implicitly contrasts with owa_help_search by naming it as the source of the id. The phrase 'the steps behind the excerpt' tells the agent exactly what content this returns relative to a search hit.

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

Usage Guidelines4/5

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

Clearly positions the tool as the follow-up to owa_help_search, since the id must come from a search hit. It does not state explicit exclusions or what to do if you already know the document another way, but the trigger condition is unambiguous.

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