`get_page`

Get a documentation page as raw Markdown content.

Input Schema

json

{
  "type": "object",
  "properties": {
    "project": {
      "type": "string",
      "description": "Project ID (e.g. 'kli')"
    },
    "section": {
      "type": "string",
      "description": "Section slug"
    },
    "page": {
      "type": "string",
      "description": "Page slug"
    }
  },
  "required": [
    "project",
    "section",
    "page"
  ]
}

Example

json

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_page",
    "arguments": {
      "project": "nix-effects",
      "section": "diag-hints",
      "page": "pidom-not-a-type"
    }
  }
}

Applicable Error Codes

Code	Name	When
`-32001`	`tool-not-found`	The named MCP tool is not registered in the active server registry.
`-32002`	`tool-execution-error`	A tool was invoked successfully but its body raised an error.
`-32003`	`resource-not-found`	The requested MCP resource URI is not registered.
`-32004`	`prompt-not-found`	The named MCP prompt is not registered.
`-32005`	`tool-example-invalid`	A tool's bundled :example payload failed validation against its auto-generated :schema.
`-32600`	`invalid-request`	JSON-RPC 2.0 invalid-request: the JSON is well-formed but does not conform to the JSON-RPC envelope.
`-32601`	`method-not-found`	JSON-RPC 2.0 method-not-found: the requested method is not registered on the server.
`-32602`	`invalid-params`	JSON-RPC 2.0 invalid-params: the request 'params' value is missing required fields or carries unexpected ones.
`-32700`	`jsonrpc-parse-error`	JSON-RPC 2.0 parse-error: the server could not decode the incoming message as JSON.

Back to MCP Server