Skip to main content
Glama

Emergent.FM

Search entries

search_items
Read-only

Published entries filtered by tool, vendor, change type, a story's topic and words in the text, newest first. Searches one read of at most 500 entries, made of the last 30 shows and the newest wire rows.

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_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoWords to find in the headline, summary or text, matched without regard to case.
toolNoThe tool's exact name, matched without regard to case.
limitNoHow many entries at most, 1 to 50. Default 20.
topicNoOnly newsroom stories with this tag: models, coding_agents, agent_skills, mcp_servers, orchestration, memory_verification, personal_agents, launches, workflows. Shows and wire rows have no tag here.
vendorNoThe vendor's exact name, matched without regard to case.
change_typeNoThe exact change type, for example Pricing or Release, matched without regard to case.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description goes beyond that by disclosing the corpus boundary: one read of at most 500 entries drawn from the last 30 shows plus the newest wire rows. That recency and coverage ceiling is exactly the kind of non-obvious behavior an agent needs when interpreting empty or partial results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, both carrying load, with the filter capability front-loaded before the corpus caveat. The second sentence is slightly compressed in phrasing ('Searches one read of at most 500 entries, made of the last 30 shows and the newest wire rows'), but no sentence is wasted.

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?

With six optional parameters, full schema coverage, and no output schema, the description supplies the one thing the schema cannot: the size and composition of the searchable set, which bounds what any result can contain. It stops short of explaining the returned entry shape or the default page size, but the default limit is already in the schema.

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 100%, so every parameter is already documented in structured form and the baseline is 3. The description restates the filter set without adding format, matching, or precedence semantics beyond what the schema already specifies (case-insensitive exact match, the topic enum's story-only restriction, the 1-50 limit range).

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 names a specific verb and resource ('Published entries filtered by tool, vendor, change type, a story's topic and words in the text, newest first') and enumerates the filter dimensions, so an agent can tell this is a filtered search rather than a plain listing. It does not contrast itself with the siblings latest_items or items_by_date, so the differentiation is left to inference.

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 the filter list: reach for this when you need to narrow by tool, vendor, change type, topic, or free text. There is no explicit statement of when to prefer this over latest_items or items_by_date, and no stated exclusions or prerequisites. The 'newest first' ordering hint is the closest thing to guidance about the alternative ordering tool.

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