Skip to main content
Glama

tactica. football intelligence

Get betting picks for a match

get_betting_picks
Read-onlyIdempotent

tactica. Betting Intelligence picks for one fixture: market, tier, chance and the best current UK bookmaker price. 18+. Paid: 2.00 USDC per call via x402 on Base.

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": {
      "fixtureId": "<fixtureId>"
    },
    "name": "get_betting_picks"
  }
}

Input Schema

NameRequiredDescriptionDefault
fixtureIdYestactica. fixture id, from list_fixtures

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely non-obvious behavior: it is a paid call at 2.00 USDC per invocation via x402 on Base, and content is 18+ restricted. That cost/payment disclosure is the kind of context an agent cannot infer elsewhere; only rate limits or no-pick behavior are absent.

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?

Two short sentences, front-loaded with the resource and its fields, then the cost. The 'tactica.' branding prefix and the '18+' fragment are small overhead but do carry real constraint information.

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?

With no output schema, the description helpfully enumerates the returned fields, and it discloses payment mechanics, which is essential before calling. Missing only edge behavior (no picks available, already-started fixture), which is minor for a one-parameter read tool.

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% with a single required fixtureId whose schema entry already says it comes from list_fixtures. The description adds no format, validity, or failure semantics beyond that, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource ('Betting Intelligence picks for one fixture') and enumerates the payload — market, tier, chance, best current UK bookmaker price — which lets an agent distinguish it from get_match_forecast or get_top_five without opening a schema. It stops short of naming the sibling it is not, so it is clear but not fully differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'for one fixture' plus the schema note that fixtureId comes from list_fixtures gives a workflow hint. There is no explicit when-to-use vs when-to-use-an-alternative guidance and no statement about pre-match vs in-play fixtures.

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.

Resources