Skip to main content
Glama

Search entries

search_entries
Read-only

Search stored RSS and Atom entries by case-insensitive text in titles, summaries, or bodies, with an option to limit results to one feed.

Instructions

Case-insensitive substring search across stored entries.

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": {
      "query": "<query>"
    },
    "name": "search_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum hits
queryYesText to match in title/summary/body
feed_idNoRestrict the search to one feed

Output Schema

NameRequiredDescriptionDefault
totalNoTotal entries matching the filters
offsetNo
entriesNo
has_moreNoTrue when offset + returned < total
returnedNoEntries in this page

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the useful behavioral detail that matching is case-insensitive substring, but it does not disclose result ordering, limit/truncation behavior, or pagination expectations.

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?

The description is a single, front-loaded sentence with no filler. Every phrase contributes either the resource being searched or the matching semantics.

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?

This is a low-complexity tool with rich structured support: full schema descriptions, annotations, and an output schema. The description covers the core matching behavior and scope, though it leaves sibling routing and result-shaping expectations implicit.

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 100%, so the schema already documents query, limit, and feed_id. The description still adds meaning beyond the schema by clarifying that query matching is case-insensitive and substring-based, which affects how an agent should formulate queries.

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 states a specific verb and resource: "search" over "stored entries," and adds that matching is case-insensitive substring. It is clear what the tool does, but it does not distinguish itself from siblings such as list_entries or get_entry.

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?

Usage is implied by "search" and the substring-matching behavior: an agent can infer this is for finding entries by text. However, there is no explicit guidance on when to use this instead of list_entries, get_entry, or other sibling tools, and no when-not guidance.

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