Skip to main content
Glama

BetSlip Doctor

Connect a sportsbook

connect_sportsbook
Idempotent

Return a 10-minute betslipdoctor.ai link (linkUrl, expiresAt) for the customer to open and finish connecting a sportsbook. The app checks the requested book and optional two-letter state; without a state it uses the account’s state when known, otherwise the sportsbook list opens. If the state list is unavailable, the sportsbook list may open instead. While linking is not allowed it answers book_link_required with consent.text, consent.privacyUrl and consent.textVersion: show the text and privacy link word for word, and only after the customer’s explicit yes call again with consent true, that consentTextVersion and a commandKey (a missing or stale version is refused). Never sees sportsbook passwords; never places a wager.

Input Schema

NameRequiredDescriptionDefault
bookYes
stateNo
consentNo
commandKeyNo
consentTextVersionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / book / pattern
      Previous value: -"^[A-Za-z0-9 ._'&-]+$"New value: +"^[A-Za-z0-9 ._&'+-]+$"
  2. Changed3 schema fields changed
    • addedInput schema / properties / commandKey
      Added value: +{
      +  "maxLength": 120,
      +  "minLength": 16,
      +  "pattern": "^[a-zA-Z0-9_-]+$",
      +  "type": "string"
      +}
    • addedInput schema / properties / consent
      Added value: +{
      +  "const": true,
      +  "type": "boolean"
      +}
    • addedInput schema / properties / consentTextVersion
      Added value: +{
      +  "maxLength": 80,
      +  "minLength": 1,
      +  "type": "string"
      +}
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the 10-minute expiry, the book_link_required refusal path with the required consent fields, the rule that a missing or stale version is refused, that the customer must give explicit yes before consent:true is called, and the safety guarantees (never sees passwords, never places a wager). This is rich behavioral context despite annotations already carrying the safety profile.

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?

Front-loaded with the primary outcome and return fields, and most sentences carry real information. It is dense and slightly run-on around the state-handling edge cases, but little is truly wasteful.

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

Completeness5/5

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

For a mutation tool with no output schema and 5 undocumented parameters, the description supplies return fields, error/refusal behavior, consent flow, and safety notes. Nothing an agent needs to call it correctly appears missing.

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

Parameters5/5

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

With 0% schema description coverage, the description compensates fully: book is the requested book, state is an optional two-letter state, consent must be true (only after explicit customer yes), commandKey is required and refused when missing or stale, and consentTextVersion must match. Every parameter's role and constraint is explained.

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

Purpose5/5

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

States a specific verb and resource ('Return a 10-minute betslipdoctor.ai link ... to finish connecting a sportsbook') and immediately names the returned fields linkUrl and expiresAt. It is clearly distinguishable from siblings like list_sportsbooks, refresh_sportsbook, and disconnect_sportsbook.

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?

Explains the state-handling conditions (uses account state when known, otherwise opens the sportsbook list, and falls back if the state list is unavailable) and the consent gating flow. It gives clear when-to-use context but does not explicitly name alternative sibling tools to route between.

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.