JMT x402 MCP Server

news_briefing

Get a multi-source news summary with sentiment analysis for any topic. Searches across sources and generates an AI-powered brief.

Instructions

AI news briefing — multi-source search + LLM summary with sentiment. Price: $0.05/call via x402 (USDC on Base mainnet).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "topic": "<topic>"
    },
    "name": "news_briefing"
  }
}

Input Schema

Name	Required	Description	Default
`topic`	Yes	Topic to brief on

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 13, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations provided, the description includes useful behavioral context such as pricing ($0.05/call) and the use of x402 payment. However, it omits other important traits like return format, authentication requirements, or rate limits.

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?

The description is extremely concise with two sentences: the first front-loads the core functionality, and the second adds critical cost information. No word is wasted.

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?

Given the tool's low complexity (one parameter, no output schema), the description covers the essential purpose and cost. However, it could be more complete by specifying output format or providing usage context among many sibling tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a single parameter 'topic'. The description adds meaning by specifying that the briefing includes multi-source search, LLM summary, and sentiment, which helps the agent understand the tool's output beyond the raw parameter.

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?

The description clearly states 'AI news briefing' and explains the functionality as 'multi-source search + LLM summary with sentiment'. This specific verb+resource combination distinguishes it from sibling tools like 'summarize' or 'market_pulse'.

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

Usage Guidelines2/5

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

The description does not provide explicit when-to-use or when-not-to-use guidance relative to sibling tools. While the purpose is clear, there is no indication of alternatives or exclusion criteria.

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