Skip to main content
Glama
proplineapi

PropLine

Official

propline_list_sports

Discover which sports PropLine polls. Returns sport keys, titles, and active status for use with other tools.

Instructions

List all sports PropLine currently polls. Returns sport keys (e.g. baseball_mlb, basketball_nba, soccer_epl) along with human titles and active status. Use this first to discover what sport_key values are valid for the other tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for propline_list_sports, which calls client().listSports() to fetch the list of sports from the PropLine API.
    handler: () => client().listSports(),
  • Input schema for propline_list_sports — an empty object with no required fields and additionalProperties set to false.
    inputSchema: {
      type: "object",
      properties: {},
      additionalProperties: false,
    },
  • src/index.ts:68-81 (registration)
    Tool definition entry for propline_list_sports within the tools array, including name, description, inputSchema, and handler.
    {
      name: "propline_list_sports",
      description:
        "List all sports PropLine currently polls. Returns sport keys " +
        "(e.g. baseball_mlb, basketball_nba, soccer_epl) along with human " +
        "titles and active status. Use this first to discover what " +
        "sport_key values are valid for the other tools.",
      inputSchema: {
        type: "object",
        properties: {},
        additionalProperties: false,
      },
      handler: () => client().listSports(),
    },
  • The listSports() method on PropLineClient that makes a GET request to /v1/sports.
    listSports(): Promise<unknown> {
      return this.request("/v1/sports");
    }
Behavior4/5

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

No annotations provided, so description carries full burden. It explains the return format (keys, titles, active status) and that it lists currently polled sports, which is sufficient for a simple read-only operation.

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 concise sentences with no wasted words. The key information is front-loaded.

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?

The description fully covers the tool's purpose and usage given zero parameters, no output schema, and low complexity.

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?

No parameters exist; baseline score of 4 applies. The description adds no parameter-specific information, which is acceptable given the lack of parameters.

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?

The description clearly states it lists all sports PropLine polls and specifies the output includes sport keys, human titles, and active status. This distinguishes it from sibling tools which focus on events, odds, etc.

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

Usage Guidelines5/5

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

Explicitly advises to use this tool first to discover valid sport_key values for other tools, providing clear guidance on when and why to use it.

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/proplineapi/propline-mcp'

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