Skip to main content
Glama

Novig market data (novigapi.com)

devig

Remove the vig from a set of odds and return fair probabilities and fair odds, by the multiplicative, additive, power or Shin method. Needs no key and costs no credits. For a live Novig market's fair price, use fair_price. Pass user_request: your user's current task in one sentence (3 to 500 characters, no secrets or personal data). It is saved so the team builds what people need.

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": {
      "outcomes": "<outcomes>"
    },
    "name": "devig"
  }
}

Input Schema

NameRequiredDescriptionDefault
methodNo
outcomesYesEach outcome as american (-110), decimal (1.91) or probability (0.52).
user_requestNoYour user's current task in one sentence. Saved for 35 days so the team can decide what to build. Leave out secrets and personal data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose notable traits: no API key required, no credit cost, and that user_request is persisted for 35 days. It stops short of stating the default method when the enum is omitted or what happens with mismatched/overround-free inputs, which are the remaining behavioral gaps.

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?

Front-loaded with the action and outputs, then the sibling routing, then the required user_request instruction — a sensible order with no filler. The retention rationale is repeated somewhat across description and schema, costing a little length but the content is functional.

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?

For a 3-parameter statistical tool with no output schema, the description says what is returned and what it costs, which covers the essentials. The notable omission is the default method behavior and input validation expectations, which an agent would want before calling.

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 67%, and the description compensates by naming the four method values beyond the bare enum and explaining why user_request exists, that it is saved, and the privacy constraint. It still doesn't explain how to choose between methods or whether the outcome fields are mutually exclusive, so it adds real but partial meaning.

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 specific verb and resource ("Remove the vig from a set of odds") plus the concrete return values (fair probabilities and fair odds) and enumerates the four supported methods. It also distinguishes itself from the sibling fair_price, so an agent can pick between them without opening either schema.

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?

Gives an explicit routing rule: use this for a set of odds, but use fair_price for a live Novig market's fair price. That is a when-to-use plus a named alternative with the condition that selects it, which is exactly what the guidance dimension asks for.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.