Skip to main content
Glama

Novig market data (novigapi.com)

search

Search Novig players and their per-stat prop pages (such as "LeBron James points"), current markets, teams, leagues, and this site's calculators, guides, glossary and API docs. Returns ids to pass to fetch. Needs no key and costs no credits.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesA player (optionally with a stat), team, league, market, calculator, guide or docs topic.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description does real work: it discloses that no key is needed and no credits are consumed, and that the payload is ids rather than full records. It omits other behaviors an agent would want, such as result count limits, ranking/ordering of matches, and how ambiguous queries (team vs. player name collisions) are resolved.

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 sentences, front-loaded with verb and scope, followed by the chaining hint and the cost/auth facts. The long enumeration is informative rather than filler, and nothing is repeated.

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 single-parameter search with no output schema and no annotations, the description covers scope, return shape (ids), and access cost. It is nearly complete; only result volume and match behavior are left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning: the query may combine a player with a stat ("LeBron James points"), and the same field spans markets, calculators, guides and docs. That compound-query format is not obvious from the schema's terse property description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (search) plus the exact resource domains: player per-stat prop pages, markets, teams, leagues, calculators, guides, glossary and API docs. It also gives a concrete query example ("LeBron James points") and states that results are ids, which separates it from the sibling entity getters (get_players, get_teams, get_markets) that return data directly.

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?

Usage is implied rather than stated: "Returns ids to pass to fetch" makes clear this is the discovery step preceding fetch. However, it never says when NOT to use it (e.g. when a direct get_players or get_leagues call is preferable), nor does it name an alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.