Skip to main content
Glama

get_entry

Retrieve one knowledge entry revision with its change history and a bounded detail page to inspect recorded decisions, preferences, or procedures.

Instructions

Read one entry revision with history and a bounded detail page.

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": {
      "entry_id": "<entry_id>"
    },
    "name": "get_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
cursorNo
entry_idYes
revision_idNo
actor_handleNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations at all, the description carries the full disclosure burden. 'Read' implies a non-mutating operation and 'bounded detail page' hints at a server-imposed page cap, but nothing is said about permissions, whether history retrieval affects cost/latency, or how revisions are resolved when revision_id is omitted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no filler, which is good, but the brevity comes at the cost of under-specification rather than being economically complete.

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

Completeness2/5

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

An output schema exists, so return values need not be described, but the tool takes five parameters with zero schema documentation, has no annotations, and mixes three concerns. Given that complexity, one terse sentence is not enough to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and none of the five parameters are documented. The description implies revision_id ('one entry revision') and page/cursor ('bounded detail page'), but leaves entry_id and actor_handle entirely unexplained, including what actor_handle scoping means for the returned data.

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

Purpose3/5

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

The verb 'Read' and resource 'one entry revision' are stated, and it hints at two additional facets (history and a bounded detail page). However, the sentence conflates three things — the revision itself, its history, and a paged detail view — without clarifying what the primary result is, and it gives no signal distinguishing it from siblings such as get_context or search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. An agent must guess whether this is the right call versus get_context or search for retrieving entry data.

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