mcp.xynaptic

news-world

Xynaptic World News Briefing v2 — curated global events (importance >= medium) aggregated from all 7 Xynaptic news feeds, cross-feed deduplicated with reinforced verification. The executive briefing for busy agents. Refreshed every 2 hours. [price: $0.020 per call, x402/USDC]

Input Schema

TableJSON Schema

Name	Required	Description	Default
`params`	No	query parameters

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 2, 2026

removedInput schema / properties / body

Removed value: -{
-  "description": "JSON body for POST endpoints (e.g. insurance, ai-chat, production-risk)",
-  "type": "object"
-}

changedInput schema / properties / params / description

Previous value: -"query parameters, e.g. {city: 'Paris', type: 'Appartement'}"New value: +"query parameters"

addedInput schema / properties / params / properties

Added value: +{
+  "items": {
+    "description": "example: [{\"topic\":\"World\",\"headline\":\"...\",\"source\":\"...\"}]",
+    "type": "string"
+  },
+  "refresh": {
+    "description": "example: \"every 2 hours\"",
+    "type": "string"
+  }
+}

addedInput schema / required
```
Added value: +[]
```

First observedOct 1, 2026

TDQS

A3.6/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose real behavior: the importance threshold, cross-feed deduplication, reinforced verification, a 2-hour refresh cadence, and the $0.020 per-call charge via x402/USDC. That pricing and cadence disclosure is genuinely useful. It still omits auth requirements, failure modes, and return shape, keeping it short of a 5.

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?

A single tight paragraph with the core scope front-loaded before the supporting details. The 'executive briefing for busy agents' line is mild marketing filler, but the sentence still earns its place as a use-case cue.

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?

For a zero-annotation, no-output-schema tool this covers cadence, filter level, dedup behavior, and price — a reasonable minimum. It never explains what a briefing item contains (topic/headline/source) or how the nested params object should be formed, so an agent still has gaps to fill.

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 reported at 100%, so the baseline is 3. The description adds nothing about the single 'params' object — its shape is only conveyed by example strings in the schema, so the description neither compensates nor detracts.

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+resource ('World News Briefing'), the aggregation scope (all 7 Xynaptic news feeds), and the filtering rule (importance >= medium). It implicitly distinguishes itself from the regional siblings (news-us, news-eu, news-asia) by being global, but never names them, so 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?

The phrase 'executive briefing for busy agents' and the 2-hour refresh hint at when this is appropriate, and the importance>=medium threshold implies it is the high-signal choice. However there is no explicit statement of when to pick this over news-us/news-eu/news-tech or any exclusion of use cases.

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

All mcp.xynaptic 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?