Agent Shopping Tracker

Search news

search_news

Read-onlyIdempotent

Search dated news. Filter with since (YYYY-MM-DD), a player slug, or words from the title, summary, or tags. Credit each item's Page URL.

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

Input Schema

Name	Required	Description
`limit`	No	How many items to return. Default 20.
`query`	No	Words to find in the title, summary, tags, or source name.
`since`	No	Only news on or after this date, YYYY-MM-DD.
`player`	No	Player slug, such as walmart.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare the tool read-only, idempotent, non-destructive, and closed-world. The description adds one genuinely useful behavioral obligation, 'Credit each item's Page URL,' but says nothing about ordering, result shape, or pagination beyond the schema's limit field.

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, front-loaded with the core action and followed by filter guidance and an attribution note. There is no redundant or filler wording.

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 simple read-only search with a fully documented four-parameter schema and annotations covering safety, the description covers purpose, filtering, and attribution adequately. Only ordering and result-set behavior are left unspecified, which is a minor gap.

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 all four parameters are already documented in the schema. The description restates since, player, and query semantics but adds no syntax, precedence, or combination rules beyond the schema.

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 opens with a specific verb and resource, 'Search dated news,' and scopes it to news items with dates. It does not explicitly contrast with any sibling, but none of the listed siblings cover news, so ambiguity is low.

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

Usage Guidelines4/5

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

It explains how to filter: by since date, player slug, or words in title/summary/tags. That gives clear usage context for combining filters, though it does not state when not to use the tool or mention any alternative.

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

All Agent Shopping Tracker tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?