JMT x402 MCP Server

analyze

Perform deep AI analysis with integrated web research on any topic. Each call costs $0.10 via x402.

Instructions

Deep AI analysis with web research. Price: $0.10/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": "analyze"
  }
}

Input Schema

Name	Required	Description	Default
`topic`	Yes	Topic to analyze

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 13, 2026

TDQS

C2.6/5.0

Behavior2/5

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

Without annotations, the description must fully disclose behaviors. It mentions web research and cost, but does not state whether the tool is read-only, what authentication is required, how results are returned, or any limitations.

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?

The description is two sentences long, efficient, and front-loaded with purpose and cost. However, it omits details that could be added without significant bloat.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has one parameter, no output schema, and no annotations, yet the description does not explain output format, response structure, or how the analysis is conducted. With many similar sibling tools, this is insufficient for an agent to choose correctly.

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?

The schema covers 100% of parameters with a description for 'topic'. The tool description adds no additional semantics beyond 'topic to analyze', so it adds no extra value; baseline score of 3 is appropriate.

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

Purpose3/5

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

The phrase 'Deep AI analysis with web research' indicates a general analysis tool, but it does not specify the type of analysis or how it differs from sibling tools like 'deep_research' or 'competitor_analysis'. The verb 'analyze' is broad, and the resource is undefined.

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 mentions a cost of $0.10/call but gives no guidance on when to use this tool versus alternatives. No criteria, prerequisites, or exclusions are provided.

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