Weather Markets Edge Desk

Convert Probability / Odds

convert_probability

Read-only

Convert between implied probability, American odds, and decimal odds. Give one value and its format and get all three back (American odds carry no commas, e.g. +441 or -200). Use for "what is +150 as a probability", "convert 62% to American odds", "decimal to implied odds".

Input Schema

TableJSON Schema

Name	Required	Description	Default
`value`	No	The numeric value to convert. Needed for a real answer, with format. Accepts a number or a numeric string ("+150", "62%", "2.5").
`format`	No	Format of `value`: probability (0–100 %), american (e.g. -200 / +150), or decimal (e.g. 2.5). One of: probability · american · decimal.

Output Schema

TableJSON Schema

Name	Required	Description
`sources`	No
`tell_user`	No	Show this sentence to the user first.
`timestamp`	No
`needs_input`	No
`decimal_odds`	No	Decimal odds.
`example_call`	No
`american_odds`	No	American odds, no commas.
`data_freshness`	No
`probability_pct`	No	Implied probability, %.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 29, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "american_odds": {
+      "description": "American odds, no commas."
+    },
+    "data_freshness": {},
+    "decimal_odds": {
+      "description": "Decimal odds."
+    },
+    "example_call": {},
+    "needs_input": {},
+    "probability_pct": {
+      "description": "Implied probability, %."
+    },
+    "sources": {},
+    "tell_user": {
+      "description": "Show this sentence to the user first.",
+      "type": "string"
+    },
+    "timestamp": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedSep 29, 2026

changedInput schema / properties / value / description

Previous value: -"The numeric value to convert. Accepts a number or a numeric string (\"+150\", \"62%\", \"2.5\")."New value: +"The numeric value to convert. Needed for a real answer, with format. Accepts a number or a numeric string (\"+150\", \"62%\", \"2.5\")."

removedInput schema / required

Removed value: -[
-  "value",
-  "format"
-]

First observedSep 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds behavior beyond that: it discloses that all three representations are returned and specifies the American-odds formatting convention (no commas, e.g. +441 or -200), which an agent would otherwise get wrong.

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?

Three short sentences, front-loaded with the conversion scope, then the input/output contract, then concrete usage examples. No filler or repetition.

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 an output schema present, the description need not explain return values, and it correctly focuses on the input contract and format conventions. Parameters, enum options, and usage triggers are all covered, so nothing needed to call this tool is missing.

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?

Schema description coverage is 100%, and the schema already supplies the enum values and the same example inputs ("+150", "62%", "2.5") used in the description. The description restates the format/example contract rather than adding new semantics, so the baseline of 3 applies.

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 (Convert) and resource (implied probability, American odds, decimal odds) with the exact transformation direction. An agent can immediately distinguish this from siblings like calculate_ev, bayes_update, or kelly_size, which perform analysis rather than unit conversion.

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?

The description gives explicit trigger phrases ("what is +150 as a probability", "convert 62% to American odds", "decimal to implied odds") and the input contract ("Give one value and its format"). It stops short of naming when NOT to use it or which sibling to prefer for derived calculations, so it is clear context without exclusions.

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

All Weather Markets Edge Desk 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.