tela

Overview Schema Source Related Servers Discussions Admin

Get page

get_page

Read-only

Retrieve a wiki page's markdown body and metadata by numeric id, plus trust signals for freshness, provenance, and disputes. Use format map for headings or values for sheet results.

Instructions

Full markdown body + metadata for a numeric page id. Includes an epistemic block — trust signals computed from the wiki's own state: freshness (age, stale, review_overdue), provenance (human / agent / sync), and corroboration vs. dispute against same-space pages. Weigh it: prefer fresh, corroborated, human-reviewed pages; treat a stale or disputed page as lower-confidence and check its listed disputes before relying on it.

Input Schema

Name	Required	Description	Default
`id`	Yes	numeric page id
`format`	No	'full' (default) returns the markdown body; 'map' returns just the heading outline (section levels + paths) and no body — cheap to read, and each path is a target for patch_page; 'values' — for a SHEET page (sheet=true), returns the computed spreadsheet as self-describing prose (formulas materialized to their numbers, styling stripped) so you read the answers, not the raw =formulas (no effect on non-sheet pages)

Output Schema

Name	Required	Description	Default
`page`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.11.0Oct 15, 2026

addedOutput schema / properties / page / properties / epistemic / properties / summary_stale
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / page / properties / sections / items / properties / in_quote
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / page / properties / status
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / page / properties / version
```
Added value: +{
+  "type": "integer"
+}
```

changedOutput schema / properties / page / required

Previous value: -[
-  "id",
-  "space_id",
-  "parent_id",
-  "title",
-  "body",
-  "position",
-  "created_at",
-  "updated_at",
-  "url"
-]New value: +[
+  "id",
+  "space_id",
+  "parent_id",
+  "title",
+  "body",
+  "position",
+  "created_at",
+  "updated_at",
+  "version",
+  "status",
+  "url"
+]

First observedv0.1.0Jul 5, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description doesn't need to restate safety. However, it adds substantial behavioral context: it explains the epistemic block's trust signals (freshness, provenance, corroboration vs. dispute) and how to interpret them. This goes beyond the annotations, providing decision-making guidance.

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?

Front-loaded with the core return, then explains the epistemic block. Every sentence earns its place, though the second sentence is fairly dense. Overall efficient.

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 an output schema present, the description needn't detail return values. It covers the key addition (epistemic signals) and their interpretation. Could mention pagination or size limits, but for a page retrieval tool it's largely complete.

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%, so the schema already documents both parameters, including the format modes. The description adds no additional parameter semantics beyond what's in the schema. Baseline 3 is appropriate.

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 (get) and resource (page) with the exact return content (full markdown body + metadata for a numeric page id). The scope is precise and clear.

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?

The description explains how to weigh the epistemic block, but does not explicitly state when to use get_page versus siblings like read_chunk, get_page_revision, or search. For a retrieval tool among many read alternatives, more routing guidance would help.

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