market-data

News search

public_search_news

Read-onlyIdempotent

Semantic news search across tracked instruments — returns matching items with a short summary and a mandatory source_url (never full article text).

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max results to return (default 10, max 20)
`query`	Yes	Natural language search query describing ONE semantic angle, e.g. 'Nebius Meta deal contract $27 billion compute capacity'
`days_back`	No	How many days back to search (default 30, max 90)
`min_similarity`	No	Minimum similarity threshold 0.0-1.0 (default 0.40)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`results`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 1, 2026
- changedOutput schema / properties / results / type
```
Previous value: -"array"New value: +[
+  "array",
+  "null"
+]
```

Changed1 schema field changedAug 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "results": {
+      "items": {},
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedAug 11, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, so the description adds real value by disclosing the output contract: matching items with a short summary and a mandatory source_url, never full article text. That is a meaningful behavioral constraint beyond structured fields.

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?

A single sentence that front-loads the core action and compresses scope, output shape, and a key limitation with no filler.

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?

All parameters are documented in schema and an output schema exists, so the description only needed to frame intent and output character, which it does. The only gap is not positioning against the overlapping sibling public_instrument_news.

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 fully documented with defaults and ranges. The description adds only the concept of semantic search and one-angle framing, which is already implied by the query parameter text.

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?

States a specific verb and resource ('Semantic news search across tracked instruments') and previews the return shape. It doesn't explicitly distinguish itself from the sibling public_instrument_news, so it stops short of a 5.

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 'semantic search' framing and the schema's 'ONE semantic angle' hint, but there is no statement of when to use this versus public_instrument_news or any other sibling, and no exclusions or prerequisites.

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

All market-data 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?