Skip to main content
Glama
lacausecrypto

Sports Hub MCP Server

by lacausecrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

squiggle: Get tips

squiggle_get_tips
Read-onlyIdempotent

Retrieve game-level tips and predictions from one or all Squiggle models, including margin, confidence, and correctness data when available.

Instructions

Get game-level tips/predictions from one or all Squiggle prediction models. Each tip includes margin, confidence, and post-hoc correctness when known.

Input Schema

NameRequiredDescriptionDefault
gameNoSpecific game id
yearNoSeason year
roundNoRound number
fieldsNoKeys to keep (comma-separated).
sourceNoModel source id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 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"
+}
    • removedInput schema / properties / game / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / round / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / source / maximum
      Removed value: -9007199254740991
  2. Changed4 schema fields changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / game / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / round / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / source / maximum
      Added value: +9007199254740991
  3. First observedv1.2.0

TDQS

A3.5/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. The description adds that tips include margin, confidence, and post-hoc correctness, which is useful output context, but it discloses no further behavioral traits such as rate limits, auth requirements, or default scope.

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 tightly written sentences with no filler. The core purpose is front-loaded and every clause carries information.

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?

The tool has 5 optional parameters and no output schema, so the description partially fills the return-value gap by listing tip fields. However, it omits default behavior when filters are absent (e.g., all games, all models), which an agent would need to invoke it correctly.

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 each parameter is already documented. The description adds slight meaning by clarifying that results can come from one or all models (relevant to the source parameter), but this is a minor addition beyond the schema.

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 (Get) and resource (game-level tips/predictions) and names the source domain (Squiggle prediction models). It implicitly distinguishes itself from siblings like squiggle_get_games, squiggle_get_teams, and squiggle_get_standings, but does not explicitly compare or name alternatives.

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?

The phrase 'from one or all Squiggle prediction models' implies the scope of use but gives no explicit when-to-use guidance or alternatives. It does not say when to prefer this over squiggle_get_games or squiggle_get_sources.

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