Skip to main content
Glama

Read record

wiki_get
Read-only

Read one record by its key: a table's row, or a log entry by its _id. Pages are read with wiki_read.

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

Input Schema

NameRequiredDescriptionDefault
keyYesThe row's key on a table, or the entry's _id on a log.
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).

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=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds the useful fact that keys resolve against two record families (table rows, log entries), but says nothing about behavior on a missing key or whether the key is scoped per page. Some added context, no contradiction.

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 zero filler; the disambiguating sibling routing is placed immediately after the core purpose statement, so the reader gets the important constraint up front.

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?

For a 3-required-parameter read tool with full schema coverage and no output schema, the description covers what the tool returns conceptually (one row or one log entry) and how it differs from page reads. Minor gap: it does not describe lookup failure behavior, which matters for a key-based get.

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%, so the schema already documents path format (wiki:page.dot.path), the org enum requirement, and the key's dual meaning. The description's key phrasing largely restates the schema's own wording, so baseline 3 applies with no meaningful surplus meaning added.

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 a precise resource (one record by key), and immediately disambiguates the two record shapes it covers: a table's row or a log entry's _id. It also names the sibling it is not (pages go through wiki_read), so an agent can route without opening either schema.

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?

Explicitly routes page reads to wiki_read, giving one clear alternative plus the condition that selects it. It stops short of covering the record-oriented siblings (e.g., listing records vs fetching one), so there is no explicit when-not guidance for the remaining catalog.

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