Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_standings

Retrieve MLB American and National League standings by date, season, and type, including expected, home/away, last-ten, ranking, and elimination fields when available.

Instructions

Get MLB standings. Returns American League and National League standings, including source-provided expected, home/away, last-ten, ranking, and elimination fields when available, using any supported standings type returned by mlb_discovery.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoSnapshot date in YYYY-MM-DD format; returns standings as of that date
typeNoStandings type
seasonNoFour-digit season; defaults to current year

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.7
    • addedInput schema / properties / date
      Added value: +{
+  "description": "Snapshot date in YYYY-MM-DD format; returns standings as of that date",
+  "type": "string"
+}
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "regularSeason",
-  "wildCard",
-  "springTraining"
-]New value: +[
+  "regularSeason",
+  "wildCard",
+  "divisionLeaders",
+  "wildCardWithLeaders",
+  "firstHalf",
+  "secondHalf",
+  "springTraining",
+  "postseason",
+  "byDivision",
+  "byConference",
+  "byLeague",
+  "byOrganization",
+  "currentHalf"
+]
  2. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / type / enum
      Added value: +[
+  "regularSeason",
+  "wildCard",
+  "springTraining"
+]
  3. Added

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose that certain fields (expected, home/away, last-ten, ranking, elimination) are only present 'when available', which sets return expectations, but it says nothing about read-only/safety profile, auth needs, or rate limits. Adequate but with clear gaps for a no-annotation tool.

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?

Two sentences, front-loaded with the core purpose and followed by return-field detail. The long clause listing optional fields is dense but each element is informative; no filler sentences.

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?

With no output schema, the description rightly spends its second sentence enumerating the returned fields, and the required/optional params are fully covered by the schema. It could be more complete by noting the current-season default behavior, but nothing essential for calling the tool is missing.

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%: date, type, and season are each documented in the schema, and the enum for type is fully enumerated. The description adds only the pointer that types come from mlb_discovery, so it neither compensates nor detracts. Baseline 3 applies.

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 and resource ('Get MLB standings') and scopes it to the American and National Leagues, which cleanly separates it from the other standings tools in the catalog (espn_standings, sofascore_standings, yahoo_sports_standings, flashscore_*). It does not name an alternative explicitly, so it lands just short of 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?

Gives actionable context by telling the agent that the valid standings types come from mlb_discovery, which is a concrete routing hint for choosing the 'type' value. It does not, however, state when to prefer this tool over another source's standings or cover date/season selection trade-offs.

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