Skip to main content
Glama

tactica. football intelligence

Get this week's Top 5

get_top_five
Read-onlyIdempotent

Top 5 Bets of the Week, released Thursday 23:00 UK time. 18+. Paid: 10.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_top_five"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 declare readOnly, idempotent, non-destructive and closed-world behavior. The description adds information the annotations do not carry: the tool is metered at 10.00 USDC per call via x402 on Base, and the content is 18+ restricted. That cost disclosure is essential for an agent deciding whether to invoke. It stops short of explaining what happens on failed or unpaid calls.

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?

Two short sentences with zero filler. The identity of the content comes first, and the operational constraints (release time, age limit, price) follow immediately.

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 zero-parameter read tool with no output schema, the description covers what the content is, when it refreshes, who it is for, and what it costs. It does not describe the shape of a returned pick or how payment settlement interacts with the call, which leaves a modest gap given the absence of an output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. No parameter detail is warranted or missing.

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?

The description identifies the specific resource returned ('Top 5 Bets of the Week') and its release schedule, which lets an agent distinguish it from siblings like get_betting_picks or get_settled_record. It is a noun phrase rather than a verb+resource, but combined with the title 'Get this week's Top 5' the purpose is unambiguous.

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?

The release timing (Thursday 23:00 UK) implies the content refreshes weekly, but the description never states when an agent should call this versus get_betting_picks or the other siblings. There are no explicit alternatives, no exclusions, and no noted prerequisites for use.

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