Skip to main content
Glama

Get entry

get_entry
Read-only

Fetch one RSS/Atom entry by ID to read its content; optionally mark it read and truncate the included body.

Instructions

Return one entry in full, optionally marking it 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": {
      "entry_id": "<entry_id>"
    },
    "name": "get_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
entry_idYesEntry id from list_entries or search_entries
mark_readNoMark the entry read as a side effect
include_contentNoInclude the item body
max_content_charsNoTruncate the body to this many characters

Output Schema

NameRequiredDescriptionDefault
idYesEntry id used by get_entry / mark_entries
urlNoLink to the item
guidYesFeed-provided unique id used for de-duplication
titleNoItem title
authorNoItem author, when provided
contentNoRaw item body (HTML or text)
feed_idYesOwning feed id
is_readNoRead flag
summaryNoPlain-text excerpt
feed_titleNoOwning feed title
fetched_atYesWhen this entry was first stored (UTC, ISO-8601)
is_starredNoStarred flag
published_atNoPublication time (UTC, ISO-8601)
content_truncatedNoTrue when content was cut to max_content_chars

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior1/5

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

The description states the tool will mark the entry read as a side effect, i.e. it mutates state, while the annotations declare readOnlyHint=true. That is a direct contradiction, and the schema confirms it: mark_read defaults to true, so mutation occurs on a default call. The contradiction is a real hazard because a harness trusting readOnlyHint may auto-approve a state-changing call.

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 zero filler: action, scope, and the side effect in that order. Nothing is padded or restated from the title.

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-value explanation is not owed, but the description mischaracterizes the side effect as "optional" when mark_read defaults to true, meaning mutation is the default behavior. It also omits that content may be truncated by max_content_chars, undercutting the "in full" claim. For a tool whose default path mutates state, this leaves the agent with an inaccurate mental model.

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 100%, so entry_id, mark_read, include_content, and max_content_chars are all documented in the schema itself. The description only gestures at two of them ("in full" ~ include_content, "marking it read" ~ mark_read) and says nothing about max_content_chars truncation, so there is no real value added beyond the schema; baseline 3 applies.

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 gives a specific verb and resource ("Return one entry in full") plus a scope qualifier and a disclosed side effect, so the agent knows exactly what the call does. It does not differentiate itself from siblings like list_entries, search_entries, or mark_entries, so it stops short of 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance. An agent cannot tell from the description why it would call get_entry instead of search_entries (which returns entries too) or mark_entries (which also flips read state). Usage is only implied by the phrase "one entry".

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