Skip to main content
Glama
Sign In

asktian

by io.github.douglasgan
OverviewDiscussionsAdmin

asktian_market_read

Get a Chinese-metaphysics signal on a binary prediction-market question (Polymarket/Kalshi style yes/no outcomes). Use when a user — or a trading agent — wants an UNCORRELATED, for-fun read on a market: 'will X happen by date Y'. Returns a lean (yes/no/neutral), a confidence, the 五行 reasoning from the resolution date's energy, and a mandatory disclaimer. This is ENTERTAINMENT and a falsifiable ritual — NOT financial advice. Always present it as a novelty signal, never as a recommendation to place a bet.

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": {
      "question": "<question>"
    },
    "name": "asktian_market_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYesThe binary market question, e.g. 'Will BTC be above $100k by 2026-12-31?'
resolve_dateNoOptional ISO YYYY-MM-DD when the market resolves. Defaults to today.
subject_birthdateNoOptional ISO YYYY-MM-DD. If the market is about a specific person (e.g. 'will X win'), their birthdate adds their bazi element to the read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

No annotations are provided, so the description carries full burden. It discloses that the tool is for entertainment, not financial advice, that it uses reasoning from resolution date energy, and that it returns a mandatory disclaimer. It describes the output as a 'lean (yes/no/neutral), a confidence, the 五行 reasoning, and a mandatory disclaimer'. No contradictions with annotations.

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 well-structured and front-loaded with purpose. Every sentence adds value, but it is slightly verbose with repeated emphasis on entertainment nature. A minor trim could improve conciseness.

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?

Given the tool's complexity (Chinese metaphysics on prediction markets) and no output schema, the description fully covers what the tool does, when to use it, what it returns (lean, confidence, reasoning, disclaimer), and its non-advisory nature. It is complete for the context.

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

Parameters5/5

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

Schema description coverage is 100%, and the description adds context beyond the schema. For example, it explains that 'subject_birthdate' is optional and 'adds their bazi element to the read' for person-centric markets. The 'resolve_date' is explained as optional with a default. This adds meaningful semantics.

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 the tool's purpose: 'Get a Chinese-metaphysics signal on a binary prediction-market question'. It specifies the type of questions (Polymarket/Kalshi style yes/no outcomes) and distinguishes itself from sibling tools by focusing on market prediction, not actions, compatibility, or daily readings.

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?

The description explicitly tells when to use the tool: 'Use when a user — or a trading agent — wants an UNCORRELATED, for-fun read on a market'. It provides example questions and includes explicit guidance: 'Always present it as a novelty signal, never as a recommendation to place a bet.'

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

All asktian toolsInspect
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