Skip to main content
Glama

get_entry

Read-only

Read a contribution, its current visibility, and the original receipt when issued.

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
entry_idYes

Output Schema

NameRequiredDescriptionDefault
entryYes
receiptYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds one useful behavioral detail—the receipt is returned only 'when issued', i.e., conditionally—but says nothing about the odd idempotentHint=false on a read, nor about access restrictions on non-public entries. Given an output schema exists, the thin behavioral layer is acceptable but not rich.

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?

A single front-loaded sentence with no filler; every clause (contribution, visibility, receipt-when-issued) conveys distinct information about the payload.

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 one-parameter read-by-id tool with an existing output schema and full annotation coverage, the description is close to sufficient—it names the resource and the notable parts of the return. The remaining gap is the lack of any statement about visibility/permission constraints or unknown-id behavior.

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 0%, so the schema supplies only a pattern constraint with no meaning for entry_id; the description implicitly establishes that the id identifies a contribution. It adds no format, sourcing, or error semantics (e.g., what happens for an unknown or non-visible id), so it only partially compensates for the coverage gap on the single parameter.

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 description uses a specific verb ('Read') plus a concrete resource ('a contribution') and enumerates what comes back: current visibility and the original receipt when issued. That is materially clearer than a bare 'get entry', though it never ties the term 'entry_id' to 'contribution' or distinguishes itself from catalog/search siblings.

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 prerequisite (e.g., needing an entry id you already hold), and no pointer to alternatives such as search_catalog for finding an entry you don't yet know. The intended usage—direct lookup by id—is only inferable from the required parameter.

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