Skip to main content
Glama

emet_page

Read-onlyIdempotent

Read one compiled topic page for an area, showing current records with cited sources, stale flags, and optional history. Writes nothing; owner only.

Instructions

Read one compiled topic page for an area slug (areas/.md). A page is a view of current records. It is not a record: this tool writes nothing, stores nothing, and the result is never written back and is not returned by recall. Every displayed line cites its source as [mem: · · · ] or [doc:<doc_id>@v]. A line with no source is dropped. Superseded and retired records stay out of the current sections; pass include_history true to show them under History only. A line is marked stale when its source has not been confirmed or revised within the area's staleness window (default 30 days; the area document may set its own). Owner only. Computed on every call, so cache_hit is false.

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": {
      "area": "<area>"
    },
    "name": "emet_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaYesArea slug, for example finances. The selector is the current areas/<slug>.md document.
as_ofNoOptional ISO date or unix seconds. The page shows records that were current at that moment. A document line cites the revision in force then, from documents_history. A revision that was never archived is absent. A superseded or retired record with no end date is still shown in this past view, labelled "end date unknown", and is not a current line. The area selector is the current area document.
include_historyNoWhen true, superseded and retired records appear under History, labelled as not current. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.2
    • changedInput schema / properties / area / description
      Previous value: -"Area slug, for example health. The selector is the current areas/<slug>.md document."New value: +"Area slug, for example finances. The selector is the current areas/<slug>.md document."
  2. Addedv0.3.1

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses that nothing is written or stored, that results are computed on every call so cache_hit is false, that unsourced lines are dropped, that staleness is flagged via the area's window (default 30 days), and that access is owner-only. These are exactly the behavioral facts an agent cannot infer from annotations or schema.

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 purpose and the file locator, then layered details. It is dense but each sentence carries information; the 'It is not a record / writes nothing / stores nothing / never written back / not returned by recall' clause is slightly repetitive but justified by the read/write ambiguity it removes.

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

Completeness5/5

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

There is no output schema, and the description compensates fully: it explains the citation format for memory and document lines, that unsourced lines are dropped, where history appears, and how staleness is labelled. Nothing an agent needs to interpret the result is missing.

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 all three parameters are already documented, including as_of's revision-in-force and 'end date unknown' semantics. The description adds the staleness-window default of 30 days and cache_hit behavior, but those are output traits rather than parameter guidance, so it sits at the baseline.

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 (Read) and resource (one compiled topic page at areas/<slug>.md), and explicitly contrasts it with records and with recall, so an agent knows exactly what it retrieves. It also implicitly distinguishes against the sibling emet_pages (plural list) by specifying 'one' page for a slug.

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?

Clear operational context: owner-only access, include_history true for superseded/retired records, and the note that this output is not returned by recall. It does not explicitly name emet_pages or recall as the alternative to use instead in a different situation, but the boundary is implied strongly enough to route correctly.

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