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. Usage: Use for a broad world news digest when the scope is global or unknown. Regional and thematic digests (news-eu, news-us, news-asia, news-tech...) are available through the xynaptic-catalog tool. [price: $0.020 per call, x402/USDC]

Input Schema

Name	Required	Description	Default
`params`	Yes	query parameters

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 3, 2026
- addedInput schema / properties / params / required
```
Added value: +[]
```
- changedInput schema / required
```
Previous value: -[]New value: +[
+  "params"
+]
```

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

A4.3/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 delivers real behavioral context: refresh cadence (every 2 hours), the filtering rule (importance >= medium), deduplication/verification behavior, and cost ($0.020 per call, x402/USDC). It falls short of describing return shape or auth mechanics, but the pricing and freshness disclosures are genuinely useful 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with identity and version, then scope, then usage routing, then pricing — a sensible information hierarchy. Slightly padded by the marketing line 'The executive briefing for busy agents,' which does not inform invocation, keeping it below a 5.

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 news-digest tool with no annotations and no output schema, the description covers freshness, filtering, aggregation, alternatives, and price — enough to call it correctly. The main omission is any hint at the return payload, which an agent would only learn at runtime.

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% and the params object is described there, so the baseline is 3. The description's only param-relevant contribution is the 'Refreshed every 2 hours' line loosely mapping to the refresh parameter; it adds no syntax or format meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (curated global events) with concrete qualifiers: importance >= medium, aggregated from all 7 feeds, cross-feed deduplicated. It explicitly distinguishes itself from the regional/thematic digests (news-eu, news-us, news-asia, news-tech) that exist as alternatives, so an agent can route without opening another schema.

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

Usage Guidelines5/5

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

Gives an explicit selection rule: 'Use for a broad world news digest when the scope is global or unknown,' and names the alternative discovery path (xynaptic-catalog) for narrower scopes. Both the when-to-use and the when-to-look-elsewhere conditions are stated.

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

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?