Skip to main content
Glama
DanielTomaro13

sportsdata-mcp

pointsbet_promotions

Retrieve live promotions for carousel display from PointsBet, allowing cross-provider comparison of betting offers.

Instructions

Live promotions for a display surface (carousel, etc.) from the promotions service.

Returns: [{id, type, title, description, ...}]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoen
displayTargetNocarousel
Behavior2/5

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

Without annotations, the description carries the full burden for behavioral disclosure. It indicates a read operation ('Live promotions') but offers no details on authentication, rate limits, or side effects. The mention of 'from the promotions service' is vague.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise at two sentences, but the brevity sacrifices completeness. It is front-loaded with purpose but omits essential details, making it less effective.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of output schema, annotations, and schema descriptions, the description is highly incomplete. It fails to clarify parameter meanings, output structure, or usage context, leaving the agent underinformed.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not explain the parameters 'lang' and 'displayTarget'. Even the return format hint does not connect to parameter usage. This is a critical gap for a 2-parameter tool.

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 clearly states the tool retrieves live promotions for a display surface like a carousel from the promotions service. It identifies the resource and scope, but does not explicitly differentiate from sibling tools like betr_promotions or sportsbet_popular_promotions.

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?

No guidance is provided on when to use this tool versus alternatives. The description lacks any conditional or contextual information that would help an agent decide between this and other promotion-related tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DanielTomaro13/sportsdata-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server