Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_search

Search MLB players, teams, and content topics by keyword; returns MLB.com typeahead suggestions for player, team, content, and search-term categories. Requires at least three characters.

Instructions

Search MLB players, teams, and content topics. Returns the same anonymous MLB typeahead categories used by MLB.com: player suggestions, team suggestions, content topics, and search terms. Queries need at least three characters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch text; 3-100 characters

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 burden and does disclose the return categories and the 3-character minimum. However it omits anything about result limits, ordering, whether content topics are paginated, or that it is a safe read-only lookup — all of which matter for a search 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 front-loaded sentences with no filler, though the second sentence partially re-lists the categories already named in the first ('player suggestions, team suggestions, content topics'), which is mild redundancy.

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?

There is no output schema, so the description usefully enumerates the returned category buckets, and the constraint is stated. It is nearly complete for a one-parameter search tool, missing only result-count/pagination behavior and explicit routing to sibling tools.

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 coverage is 100% and the single 'q' parameter is fully described as '3-100 characters', so the description's restatement of the 3-character minimum adds little. Baseline 3 applies when the schema does the heavy lifting.

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 (Search) and resource (MLB players, teams, content topics) plus the exact shape of the response (typeahead categories). It partially differentiates from siblings like mlb_player and mlb_teams by framing itself as a suggestion/typeahead surface, but never explicitly contrasts with those retrieval tools.

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

Usage Guidelines3/5

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

Calling it 'the same anonymous MLB typeahead categories used by MLB.com' implies it is an autocomplete/name-resolution tool, which is useful context, but there is no explicit when-to-use or when-not-to-use statement and no named alternative (e.g. use mlb_player once you have an ID).

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