Skip to main content
Glama
lacausecrypto

Sports Hub MCP Server

by lacausecrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

ncaa: Get scoreboard

ncaa_get_scoreboard
Read-onlyIdempotent

Get NCAA scoreboard data by sport and division, including game scores, status, and basic info, with an optional date filter.

Instructions

Get the NCAA scoreboard for a sport and division. Returns games with scores, status, and basic info.

Input Schema

NameRequiredDescriptionDefault
dateNoDate in YYYY/MM/DD format (e.g. 2024/01/15). Defaults to today.
sportYesSport name, e.g. "football", "basketball", "baseball", "soccer", "hockey", "lacrosse"
fieldsNoKeys to keep (comma-separated).
divisionYesDivision code, e.g. "fbs", "fcs", "d1", "d2", "d3"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / fields
      Added value: +{
+  "description": "Keys to keep (comma-separated).",
+  "type": "string"
+}
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.2.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the safety profile is covered without the description. The description adds a return-content summary ('games with scores, status, and basic info'), which is useful given there is no output schema, but it says nothing about live vs final scores, refresh behavior, or result size.

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 short sentences, front-loaded with the action, and both sentences carry information. There is no filler or 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?

For a simple read-only scoreboard call with full schema coverage, this is nearly sufficient; the return summary stands in for the missing output schema. It falls short only on live/real-time behavior and how many games to expect.

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%, so all four parameters, including the date format and field keys, are already documented in the schema. The description only restates the required sport/division scope and adds no syntax or default details beyond it.

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 the NCAA scoreboard) and scopes it by sport and division, which is clearly distinguishable from siblings like ncaa_get_schedule or ncaa_get_game. It does not, however, explicitly name or rule out those siblings.

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

Usage Guidelines2/5

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

The description gives no when-to-use guidance and no alternatives. With ncaa_get_schedule, ncaa_get_game, espn_get_scoreboard and ncaa_get_rankings all in the sibling list, the agent receives no signal on why this tool should be chosen over them.

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