Skip to main content
Glama

search

Read-onlyIdempotent

Find stored AI news items by text, publish time, category, or source; combine optional filters and return matching items newest first.

Instructions

Search stored Items by text, publish time, Category and Source, in any mix.

    Use for a question about a subject or time span, such as last week's Engineering
    Items about MCP or what was published today, and whenever `whats_new` is not
    clearly asked for. Every filter is optional; an omitted one matches every Item.
    `query`: the title or the whole summary contains it (case-insensitive).
    `since` / `until`:
    published at or after `since` and before `until`, ISO 8601; a time without an
    offset, or a date alone (midnight), is UTC. `categories`: in any of them (News,
    Applications, Engineering, Models; see `whats_new`). `sources`: from any of these
    Source ids (see `list_sources`). An empty `categories` or `sources` list matches
    nothing. Results are newest first, at most `limit` (default 20). A summary shown is
    plain text cut to `summary_length`, about 500 characters by default; a shorter
    length skims many Items by title, 0 shows none, and `read_item` gives the full text.
    Searching never moves a Checkpoint.
    

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
sinceNo
untilNo
sourcesNo
categoriesNo
summary_lengthNo

Output Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A5/5.0
Behavior5/5

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

The annotations already declare read-only, idempotent, non-destructive behavior, but the description adds important context: results are newest first, capped by `limit` with default 20, and searching never moves a Checkpoint. It also explains empty category/source list behavior and summary truncation, which are not derivable from the annotations.

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 front-loaded with purpose and usage, then moves through each parameter systematically. Despite its length, every sentence adds operational meaning, and the parameter-by-parameter structure is easy to scan.

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

Completeness5/5

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

For a seven-parameter search tool with an output schema and annotations already covering safety, the description supplies everything an agent needs: filtering semantics, time handling, ordering, limit behavior, summary truncation, empty-list edge cases, and checkpoint side effects. No material gaps remain.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden and does so thoroughly. It defines case-insensitive `query` matching against title or summary, ISO 8601 semantics and UTC defaults for `since`/`until`, enum values for `categories`, Source ids for `sources`, empty-list matching behavior, and `summary_length` truncation semantics.

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

Purpose5/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 stored Items by text, publish time, Category, and Source, in any mix. It clearly distinguishes this from `whats_new` by saying to use search whenever `whats_new` is not clearly asked for, so an agent can select it without inspecting siblings.

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

Usage Guidelines5/5

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

It gives explicit usage context for subject or time-span questions, names `whats_new` as the counter-case, and routes full-text retrieval to `read_item`. The guidance is directly actionable and leaves little ambiguity about when to use this tool versus alternatives.

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

Deploy Server

Other Tools