Wever Labs Agentic Rails

Look up one market’s estimated fair price

fair-value

Read-onlyIdempotent

Name one prediction market or paste its Kalshi or Polymarket ticker or URL. Plain game names resolve to outcome choices when several contracts match. Returns one existing thesis-model fair-price estimate, its original comparison and timestamps, plus matched source-labelled quotes from Kalshi, Polymarket and Novig when available. Free anonymous access. No wallet or payment is required. POST /api/fair-value. Human example: https://weverlabs.com/fair-value/.

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": {
      "market": "<market>"
    },
    "name": "fair-value"
  }
}

Input Schema

Name	Required	Description	Default
`market`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent and non-destructive semantics, and the description adds real context beyond them: results are pre-existing estimates with original comparison and timestamps, quotes are source-labelled, and access is anonymous with no wallet or payment. It doesn't say what happens when no estimate exists, which keeps it at 4.

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?

Front-loaded with the action and input forms, then returns, then access terms, ending with a human example URL. Each sentence carries distinct information; nothing is redundant padding.

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?

An output schema exists, so return values needn't be detailed, yet the description still previews the payload shape (estimate, comparison, timestamps, quotes). The only gap is failure/empty-result behavior, which an agent would otherwise have to guess.

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 0%, so the description must carry the meaning of the single 'market' parameter — and it does, spelling out that names, Kalshi/Polymarket tickers, and URLs are all valid inputs plus the disambiguation behavior. Length/pattern constraints are left to 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 concrete verb and resource ('Look up one market's estimated fair price') and immediately scopes it to prediction markets with Kalshi/Polymarket tickers. That is specific enough to separate it from the payment/work-order siblings that dominate the list.

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?

Explains accepted invocation forms (plain game name, ticker, or URL) and what happens when a name matches several contracts ('resolve to outcome choices'). It doesn't name alternatives or say when not to use it, so it stops short of a 5.

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

All Wever Labs Agentic Rails 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?