Skip to main content
Glama

undocsend docs

Read an undocsend docs page

get_doc
Read-onlyIdempotent

Return one undocsend docs page (or /features, /pricing, /security) as markdown. The path must be one returned by search_docs or list_docs.

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": {
      "path": "<path>"
    },
    "name": "get_doc"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesA docs path from search_docs or list_docs, e.g. "/docs/agreements/ndas" or "/pricing". A full undocsend.com URL or a .md URL also works.

Output Schema

NameRequiredDescriptionDefault
urlYesThe HTML page.
pathYesSite path; pass it to get_doc.
titleYes
sectionYes
markdownYes
truncatedYes
markdownUrlYesThe same page as markdown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and non-open-world, so the safety profile is covered. The description adds the markdown output form and the accepted path variants (docs path, full URL, .md URL), but says nothing about not-found/error behavior, page size, or truncation for large pages.

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?

Two short sentences with no filler: the operation and output format come first, then the sourcing constraint. Every clause carries information an agent needs.

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?

With a rich annotation set, a fully documented single required parameter, and an output schema that carries return-value detail, the definition covers what an agent needs to call it. The only missing piece is failure behavior for an invalid or stale path.

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 description coverage is 100% and the schema already supplies examples and the URL/.md fallback, so the parameter is fully self-documenting. The description only reinforces the source constraint (must come from search_docs or list_docs), adding minimal meaning beyond the schema.

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 (Return), a specific resource (one undocsend docs page), and the return format (markdown), plus concrete path examples (/features, /pricing, /security). An agent can immediately tell this is a single-page fetch, distinct from the sibling list_docs and search_docs enumeration tools.

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?

Gives a clear prerequisite: the path must be one returned by search_docs or list_docs, which establishes the intended workflow order and implies this tool is the follow-up step. It does not explicitly state when NOT to use it, but the sequencing constraint does most of the routing work.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.