Skip to main content
Glama

Read records

wiki_records
Read-only

Read records by time with pagination. Keyed pages (tables) sort by key; other pages (logs) sort by time. One record by its key is wiki_get.

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>",
      "org": "<org>"
    },
    "name": "wiki_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgYesslug of the organization whose wiki to use. Required on every call, even when only one organization is listed; a path never names it.
pathYesThe wiki's name, a colon, then the page's dot-separated path (general:docs.deploy).
limitNo
sinceNoRecords at or after this ISO-8601 time.
untilNoRecords before this ISO-8601 time.
cursorNoContinue the previous read.
latestNo
reverseNoNewest first, or highest key first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare read-only, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely useful sorting semantics (key-ordered tables versus time-ordered logs) but says nothing about pagination limits, ordering defaults, or what a returned record contains – and there is no output schema to cover that gap.

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?

Three short, front-loaded sentences with no filler; the primary purpose comes first and the sibling disambiguation last. The compression is aggressive enough that some sentences read as shorthand rather than explanation.

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?

Missing justification placeholder.

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 75%, so the schema already documents org, path, since, until, cursor, and latest. The description's key-versus-time sorting note explains why reverse means "highest key first" on tables and "newest first" elsewhere, which is real added meaning, but it says nothing about since/until interaction with keyed pages or the latest/cursor combination rules.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The definition states a specific verb and resource ("Read records ... with pagination") and immediately separates it from wiki_get for single-record-by-key reads. What a "record" actually is on a wiki page is left implicit, which keeps it from a 5.

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?

It explicitly routes the single-key-by-key case to wiki_get, so the agent knows which sibling to pick for one record. It gives no guidance on when to choose cursor-based paging versus since/until versus latest, or what happens with time ranges on keyed pages.

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.

Resources