New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

score_prob

Market-implied correct-score probabilities for ONE football match — ONE call. Inverts the de-vigged 1x2 (power de-vig) + totals prices into a bivariate-Poisson (Dixon-Coles) score grid and returns the top-K scorelines with probabilities, the fitted goal rates (lambda_home/lambda_away), and how mu...

SERVERInfersports SOURCEhttps://api.infersports.dev/mcp
Low RISK CLASS
Category Read
Parameters 41 required
Recommended Allowedsee the rule below
Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/dev-infersports-infersports/score-prob.md

What score_prob does on Infersports

AI agents call score_prob to retrieve information from Infersports without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
top integer
date object
query string Yes
sport object

Parameters from the server's own tool schema.

Why score_prob is rated Low

This tool queries and transforms existing odds/pricing data into derived probability estimates for a single match. It performs statistical analysis (Dixon-Coles Poisson fitting) on market data but neither creates, modifies, executes external operations, nor deletes anything. It is strictly informational retrieval with no side effects, fitting the Read category cleanly.

From the tool's definition Tool description states 'Read-only' server; 'score_prob' inverts existing market prices into probabilities and returns analysis results with no modification of underlying data.

Questions about score_prob

What does the score_prob tool do? +

Market-implied correct-score probabilities for ONE football match — ONE call. Inverts the de-vigged 1x2 (power de-vig) + totals prices into a bivariate-Poisson (Dixon-Coles) score grid and returns the top-K scorelines with probabilities, the fitted goal rates (lambda_home/lambda_away), and how much probability mass the list covers. The asian-handicap fair price is held out of the fit and reported as ah_ev_check (≈0 means the three markets are internally consistent). This is the market's own distribution, never an InferSports prediction. Football only, one match per call. Args: query: natural-language fixture, e.g. "Mexico vs South Africa" or a single team. sport: optional filter; only "football" is supported by this tool. date: optional UTC date "YYYY-MM-DD" to disambiguate same-name fixtures. top: how many scorelines to return (default 5, max 10). It is categorised as a Read tool in the Infersports MCP Server, which means it retrieves data without modifying state.

What parameters does score_prob accept? +

score_prob accepts 4 parameters: top, date, query, sport. Required: query. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on score_prob? +

Register the Infersports MCP server in PolicyLayer and add a rule for score_prob: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Infersports. Nothing to install.

What risk level is score_prob? +

score_prob is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit score_prob? +

Yes. Add a rate_limit block to the score_prob rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block score_prob completely? +

Set action: deny in the PolicyLayer policy for score_prob. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides score_prob? +

score_prob is provided by the Infersports MCP server (https://api.infersports.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Infersports, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Infersports's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.