Skip to main content
Glama

tactica. football intelligence

Get settled picks

get_settled_record
Read-onlyIdempotent

Settled tactica. picks with result and price, 20 per page. Paid: 1.00 USDC per call via x402 on Base.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_settled_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNopage number, 20 settled picks per page

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, closed-world read, so the bar is lower, and the description still adds two operationally important facts: pagination of 20 records and a paid access model (1.00 USDC per call via x402 on Base). It does not explain what fields accompany 'result and price' or how settlement timing affects availability, which keeps it from a 5.

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?

Three short fragments, front-loaded with what the tool returns, then pagination, then cost. Nothing is padded, though the opening fragment's grammar ('Settled tactica. picks') costs a moment of parsing clarity.

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 one-parameter read tool with no output schema and full annotation coverage, the description supplies the essentials an agent needs: what a record contains, page size, and the paid-call requirement. The remaining gap is that it never defines what 'settled' means operationally (e.g. completed fixtures only).

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% for the single page parameter (with default 1, range 1-9999), so the schema carries the semantics. The description only restates the page size, adding no new meaning beyond what is already structured.

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 and scope: settled picks that include result and price. The word 'settled' implicitly separates it from unsettled pick siblings, but no sibling is named and the fragment 'Settled tactica. picks' is slightly garbled, so differentiation is left to inference.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of the alternatives (get_betting_picks, get_track_record), so an agent must guess that this is the post-event/historical view. The only conditional information given is the payment requirement, which is about cost rather than tool selection.

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