get_sharp_line
Answer an odds question about a fixture in ONE call (natural language in, worked line out). Resolves the fixture, picks the consensus line, the best price per outcome across books, and de-vigged fair odds from the sharpest book — returning a ready-to-read summary plus the full comparison. Prefer ...
This record as markdown: /tools/dev-infersports-infersports/get-sharp-line.md
What get_sharp_line does on Infersports
AI agents call get_sharp_line 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
date | object | — | |
query | string | Yes | |
sport | object | — | |
format | string | — | |
period | string | — | |
verbosity | string | — | |
market_type | string | — |
Parameters from the server's own tool schema.
Why get_sharp_line is rated Low
This is a data retrieval tool that queries betting odds information and returns analytical summaries. It has no side effects, does not modify data, and does not execute arbitrary code or commands. The blast radius of misuse is minimal—an agent could only retrieve odds information it shouldn't have access to, not manipulate markets or financial systems.
From the tool's definition Tool description states 'Read-only' for entire server. The tool 'get_sharp_line' retrieves and returns odds data: 'picks the consensus line, the best price per outcome across books, and de-vigged fair odds from the sharpest book — returning a ready-to-read…
Attacks that exploit this kind of access
The rule that runs get_sharp_line safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Infersports, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_sharp_line, this is the rule to start with:
get_sharp_line is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Infersports, apply this rule, and every get_sharp_line call is checked against it from then on.
Questions about get_sharp_line
Answer an odds question about a fixture in ONE call (natural language in, worked line out). Resolves the fixture, picks the consensus line, the best price per outcome across books, and de-vigged fair odds from the sharpest book — returning a ready-to-read summary plus the full comparison. Prefer this over chaining find_match → compare_lines. Args: query: natural-language fixture, e.g. "Arsenal vs Man City" or a single team. market_type: "1x2", "asian_handicap" (default) or "totals". period: "full_time" (default) or "half_time". format: odds format — decimal | hk | malay | american | indonesian | probability. sport: optional filter — "football" or "basketball". date: optional UTC date "YYYY-MM-DD" to disambiguate same-name fixtures. verbosity: "full" (default) or "terse". "terse" empties the per-book books array inside comparison to save tokens; the summary and worked numbers are kept either way. On an ambiguous query, status is "ambiguous" and ask_user carries a disambiguation prompt — do not assume a match; ask the user or re-call with a more specific query. A decision block (safe_to_proceed / ask_user / next_action) pre-computes the go/no-go — branch on it instead of re-judging the result. It is categorised as a Read tool in the Infersports MCP Server, which means it retrieves data without modifying state.
get_sharp_line accepts 7 parameters: date, query, sport, format, period, verbosity, market_type. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Infersports MCP server in PolicyLayer and add a rule for get_sharp_line: 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.
get_sharp_line is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_sharp_line 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.
Set action: deny in the PolicyLayer policy for get_sharp_line. 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.
get_sharp_line 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.
This server
Across the catalogue