Skip to main content
Glama
Sign In
Outline MCP Server

Outline MCP Server

by bysonte
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Obtener documento de Outline

outline_get_document

Retrieve a specific document from Outline by providing its unique identifier. Get full document details instantly.

Instructions

Obtiene un documento concreto de Outline por ID.

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": "outline_get_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesID del documento a recuperar

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as idempotency, authentication requirements, or error conditions. The description is too minimal to inform the agent about side effects or constraints.

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?

The description is concise and front-loaded with the key action and resource. One sentence suffices for a simple retrieval tool, though it lacks structural elements like usage notes or examples.

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

Completeness3/5

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

Given the low complexity (one param, no output schema, no nested objects), the description is minimally adequate. It could be improved by mentioning that it returns the full document object or by noting if the tool is read-only.

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% for the single parameter 'id', which has a clear description. The tool description adds little beyond restating that it retrieves by ID, so it meets the baseline without providing extra context.

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 clearly states the verb 'obtiene' (gets) and the resource 'documento concreto de Outline por ID' (specific document by ID), which effectively distinguishes it from sibling tools like outline_list_documents and outline_search_documents.

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 is provided on when to use this tool versus alternatives. However, the name and context of sibling tools imply it is for retrieving a single document by its ID when the ID is known, which is a common pattern.

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

Deploy Server

Other Tools