Skip to main content
Glama

IKANGAI AI News

Search AI news

search_stories
Read-onlyIdempotent

Search AI news stories by words in the text, with optional filters. All words must match.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoWords to look for.
sinceNoOnly stories published on or after this ISO 8601 date.
topicNoOnly this topic, such as Models or Policy & Regulation.
statusNoOnly stories with this reliability status.
companyNoOnly stories about this organisation.
change_typeNoWhat kind of change: capability (New capability), breaking_change (Breaking change), outage (Outage), pricing_and_limits (Pricing and limits), security (Security), regulation (Rules and regulation), business (Business), research (Research), other (Other)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral rule — "All words must match" (AND semantics) — but says nothing about result ordering, pagination, or what a zero-match case looks like.

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 short sentences, zero filler, with the core action front-loaded and the matching rule as the immediately following qualifier. Nothing could be removed without losing information.

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

Completeness3/5

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

With seven all-optional parameters, rich enum descriptions and a full annotation set, the tool is well covered structurally. The gap is that no output schema exists, so the description could have said what a result entry contains or how results are ordered, and it does not.

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 86%, so nearly every parameter (query, since, topic, status, company, change_type) is already documented in structured form, which sets the baseline at 3. The description contributes only the AND-matching rule for query and never mentions the limit parameter's default or 25 cap.

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 ("Search AI news stories by words in the text") and adds scope via "with optional filters." It is clearly distinct from a browse-style sibling like latest_stories or a single-item fetch like get_story, though it never explicitly says so.

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 phrase "by words in the text, with optional filters" — an agent can infer this is the keyword-search path rather than the browse path. However, there is no explicit when-to-use/when-not statement and no mention of which sibling to pick for unfiltered browsing.

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