Skip to main content
Glama
Sports Hub MCP Server

Sports Hub MCP Server

ncaa: Get news

ncaa_get_news
Read-onlyIdempotent

Retrieve current NCAA news and filter results by sport when needed. Omit the sport filter to get coverage across all NCAA sports.

Instructions

Get the latest NCAA news, optionally filtered by sport.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ncaa_get_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
sportNoSport name, e.g. "football", "basketball". Omit for all sports.
fieldsNoKeys to keep (comma-separated).

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.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds nothing beyond that: no indication of recency window, result volume, pagination, or how "latest" is bounded, which is the kind of context that would earn credit here.

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?

A single short sentence with the action and scope front-loaded and zero filler. Appropriately sized for a simple two-parameter read tool.

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 read-only news fetch with full schema documentation and annotations covering safety, the description is largely sufficient. The only real shortfall is the absence of any disambiguation from the near-identical espn_get_news sibling.

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% – both "sport" and "fields" are documented with examples and the omit-for-all behavior. The description's "optionally filtered by sport" merely restates what the schema already says, so the 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 the latest NCAA news") and names the optional filter, so the agent knows exactly what the tool returns. It does not distinguish itself from the sibling espn_get_news, which covers a similar news surface, 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 Guidelines2/5

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

The description implies a basic use case (fetch NCAA news) and mentions the sport filter, but offers no when-to-use guidance, no exclusions, and no routing advice against the closely related espn_get_news sibling. An agent must infer selection on its own.

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