Skip to main content
Glama

Prior Ledger

get_entry

Read-only

Fetch one entry by its id (the full 64 hex characters, or a unique prefix of at least 8), e.g. one named in another entry's basis.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

readOnlyHint=true and openWorldHint=false already declare this as a safe, closed-world read, so the description need not re-state safety. It adds nothing about behavior beyond that: no statement of what happens on an ambiguous prefix, a malformed id, or a missing entry. That ambiguity-handling detail is exactly the behavior an agent would need for a prefix-matching lookup.

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?

One sentence, front-loaded with the verb and resource, then the format constraint, then a discovery hint. No filler and nothing buried.

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 single-parameter read with no output schema, the description covers what the tool does and the exact input format, which is the bulk of what matters. The residual gap is failure/ambiguity behavior, minor for a lookup of this simplicity.

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

Parameters4/5

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

Schema coverage is 0% and the schema only types id as a plain string, so the description carries the full burden - and it does: full 64 hex characters or a unique prefix of at least 8. That is a concrete, non-obvious format constraint that meaningfully exceeds the schema. It loses a point for not saying what occurs when a prefix matches multiple entries despite requiring uniqueness.

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?

"Fetch one entry by its id" gives a specific verb, resource, and lookup key, and the single-entry scope implicitly contrasts with the list/search siblings. It stops short of naming an alternative such as get_thread or search_precedent, so an agent must infer the boundary itself.

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 clause "e.g. one named in another entry's basis" usefully tells the agent where a valid id comes from, which is real usage context. However, there is no guidance on what to do without an id (e.g. search first) and no stated exclusions, so usage is implied rather than directed.

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.