Asia Pulse

Chain Semis

chain_semis

Read-only

Korea semiconductor axis only: betas, each session's deviation from the model with percentile, sector news events, HS 8542 export ledger and an analyst brief. Every response lists units for its numbers, ISO 8601 timestamps with time zones, and per-section sources with links and freshness. Price: $0.1 USD per call. Payment: x402. Inside MCP, send Base USDC in _meta['x402/payment'] and the data is returned in this call; without payment the tool returns the payment requirements. Over HTTPS, https://asia-pulse.com/chain/semis accepts Base USDC or X Layer USD₮0. No arguments.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "chain_semis"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 27, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds substantial context beyond them: exact price ($0.1 USD/call), the x402 payment mechanism, the specific fallback behavior when unpaid (returns payment requirements), and the dual MCP/HTTPS invocation paths. It also documents response conventions (units, ISO 8601 timestamps with time zones, per-section sources and freshness), which no annotation covers.

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 dense but earns its length: it front-loads scope and payload, then moves to payment mechanics and response guarantees. A few clauses (dual payment rails) could be tightened, but no sentence is wasted filler.

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

Completeness5/5

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

With no output schema, the description compensates by describing what a response contains (metrics, percentile, ledger, brief) and its formatting guarantees. Combined with full payment and invocation instructions, an agent has everything needed to call it and interpret the result.

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?

The tool takes zero parameters; the description's 'No arguments.' confirms this and the schema is trivially complete. No further parameter semantics are needed, so this is at the zero-parameter baseline with explicit confirmation.

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 names a specific verb-less but content-rich resource: 'Korea semiconductor axis only' with an enumerated payload (betas, session deviation with percentile, sector news events, HS 8542 export ledger, analyst brief). This precisely differentiates it from the sibling chain_defense, chain_power, japan, and chain tools.

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

Usage Guidelines4/5

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

'Korea semiconductor axis only' gives a clear scope condition that implicitly routes agents to chain_defense/chain_power for other sectors, though it never names those alternatives explicitly. The payment flow guidance (x402 _meta key inside MCP vs. HTTPS endpoint) is unusually clear about how to invoke successfully.

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

All Asia Pulse 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?