ONES Doc MCP

Get ONES Document Outline

get_doc_outline

Read-onlyIdempotent

Fetch the section outline and size metadata for a ONES doc ref to preview its structure and scope before reading the full content.

Instructions

Return section outline and size metadata for a ONES doc ref.

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": {
      "ref": "<ref>"
    },
    "name": "get_doc_outline"
  }
}

Input Schema

Name	Required	Description	Default
`ref`	Yes

Output Schema

Name	Required	Description	Default
`doc`	Yes
`sections`	Yes
`section_count`	Yes
`estimated_chars`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.1.0Oct 5, 2026
Removedv2.0.1Jul 26, 2026
First observedv1.4.0Jun 14, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description adds limited behavioral context: it specifies the tool returns section outline and size metadata. No additional side effects or prerequisites are disclosed.

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?

Single sentence of 10 words, no unnecessary information. Every word contributes to the purpose.

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?

Given the simple input (one param) and existence of an output schema, the description sufficiently covers the tool's role. It could elaborate on what 'size metadata' entails, but is adequate for selection and invocation.

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?

The schema has one parameter 'ref' with 0% description coverage. The description clarifies that 'ref' is a ONES document reference, adding meaning that the schema lacks. However, it does not provide format constraints or examples.

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?

The description uses a specific verb ('Return') and resource ('section outline and size metadata for a ONES doc ref'). It clearly distinguishes from sibling tools like get_doc (full document) and get_doc_section (specific section).

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?

No explicit guidance on when to use or avoid this tool. The purpose is clear from context and sibling names, but the description does not state when it is preferable over alternatives such as get_doc or get_doc_section.

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