Skip to main content
Glama

Distribute Software

Search tech stories

search_stories
Read-onlyIdempotent

Search the archive of technology stories and AI lab releases by keyword or topic. Returns matching stories with their original URL, date, source, the companies they are about, and a siteUrl on distribute.software.

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>",
      "context": "<context>"
    },
    "name": "search_stories"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost results to return. Default 20.
queryYesWhat to look for, e.g. 'GPT-6 launch' or 'EU AI Act'.
sinceNoOnly stories on or after this day, YYYY-MM-DD.
companyNoOnly stories about this company: a slug from list_companies.
contextYesA few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other personal details.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile needs no restating. The description adds real value by enumerating the returned fields (original URL, date, source, companies, siteUrl) for a tool with no output schema. It stops short of describing ordering, truncation, or how the limit interacts with result counts.

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?

Two sentences, zero filler, with the search scope stated first and the return shape second. Nothing in it is redundant with the title or repeats schema detail.

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 seven-parameter read-only search with full schema coverage and no output schema, the description covers both the query semantics and the return contract, which is the main gap it needed to fill. What remains unsaid — result ordering and pagination behavior — is minor.

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 every parameter including the analytics context/llm_model/conversation_id is already documented in the schema. The description adds no syntax, defaults, or format hints beyond that, so the baseline of 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?

Names a specific verb and resource: search over an archive of technology stories and AI lab releases, by keyword or topic. It does not explicitly distinguish itself from siblings such as get_story or get_today, but 'search ... by keyword' is specific enough for an agent to recognize it as the retrieval-by-query tool.

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?

The description implies when to use it (when you have a keyword or topic to look up) but gives no explicit when-not guidance and names no alternative. The schema does point at list_companies for the company slug, but that routing lives in the schema, not the description.

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