Skip to main content
Glama

Schedule

get_schedule
Read-onlyIdempotent

Use for upcoming fights: every scheduled bout in the next N days (default 30) with the current moneyline from any book that has posted one. Costs 2 credits. Prices are market information; no tool places, accepts or tracks wagers.

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_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoDays ahead (default 30, max 180).
leagueNoLeague. Defaults to mma. One of: mma, pfl, bellator.

Output Schema

NameRequiredDescriptionDefault
daysYes
boutsYes
countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: a 2-credit cost, the fact that coverage depends on books having posted a line, and an explicit scope disclaimer that no wagering occurs. It does not discuss result size or pagination, but the output schema likely handles shape.

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?

Three short sentences, front-loaded with the use case, then cost, then scope. No filler and no repetition of the schema's bounds.

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 two-optional-parameter read tool with full annotations and an output schema, the description covers purpose, cost, coverage variability and legal scope — everything an agent needs before calling. The only omission is any hint about league scoping, which the schema already fully specifies.

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%, so both parameters are already documented including the 30/180 bounds and the league enum. The description restates the default window ('default 30') without adding format or behavior detail and never mentions the league parameter at all. Baseline 3 applies when the schema does the heavy lifting.

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 gives a specific verb-resource pair and scope: 'every scheduled bout in the next N days (default 30) with the current moneyline from any book that has posted one.' An agent knows it returns an upcoming-fight list joined with prices, which separates it from line-movement or single-fight lookups. It never names a sibling tool explicitly, so differentiation is inferred rather than stated.

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

Usage Guidelines4/5

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

'Use for upcoming fights' is an explicit when-to-use trigger anchored to a time window, which is clearer than most. There are no when-not conditions and no named alternative for historical or per-event odds, leaving the agent to reason about the boundary itself.

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.