Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_discovery

Discover MLB.com navigation sections and supported Stats API values for leagues, divisions, game types, filters, and leaderboards before calling MLB endpoints.

Instructions

Discover MLB sections and Stats API values. Returns MLB.com's live navigation tree, including hidden nodes labeled with visibility, and the MLB-only value sets for leagues, divisions, game types, roster types, standings types, stat groups, supported stat types, leader categories, MLB Pipeline prospect filters, league-stats hitter positions and player pools, and observed Baseball Savant leaderboard categories and filters including Top Performers, ABS Challenges, Expected Statistics, Outs Above Average, Arm Strength, Arm Value, Home Runs, Percentile Rankings, Pitch Movement, Rolling Windows, Pitcher Arm Angle, Year-to-Year Changes, Catcher Blocking, Catcher Framing, Catcher Throwing, First Base Receiving, and Fielding Run Value. Use these values to discover sections and supported filters before calling MLB endpoints.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose useful behavior: the navigation tree is live and includes hidden nodes labeled with visibility, and the value sets are MLB-only. It says nothing about caching, auth requirements, rate limits, or response shape, so a 3 is appropriate for a read-only discovery tool.

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

Conciseness2/5

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

The middle sentence is an unpunctuated mega-list enumerating every Baseball Savant leaderboard category (Top Performers, ABS Challenges, Catcher Framing, etc.), which is return-value content that belongs in a schema or example, not a description. The most actionable sentence, the when-to-use guidance, is buried at the very end after the wall of nouns.

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

Completeness3/5

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

There is no output schema and no parameters, so return content is the description's job, and it does attempt to enumerate what comes back. However, the coverage is an unstructured dump rather than a usable map of the response, and nothing indicates format, keys, or how to consume the value sets.

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 parameter semantics are not applicable and the baseline of 4 applies. There is no input for the description to clarify.

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?

States a specific verb+resource: it discovers MLB sections and Stats API value sets, and the second sentence spells out the concrete payload (navigation tree plus league/division/game-type/stat-type value sets). An agent can tell it apart from data-fetching siblings like mlb_teams or mlb_statcast because this one is the metadata/enumeration entry point. It never names a sibling explicitly, so it stops short of a 5.

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?

The final sentence gives clear context: 'Use these values to discover sections and supported filters before calling MLB endpoints.' That tells the agent when to reach for it (pre-flight lookup) without naming any exclusion or alternative tool, so it is clear but not exhaustive.

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

Deploy Server

Other Tools