HeatCheck Agent API

Search HeatCheck

search

Read-only

Ask a question in plain language. Returns the most relevant passages from HeatCheck's public pages, each with its canonical URL to cite, plus its free sample day. Set site to all to search every Fron Research site.

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

Name	Required	Description
`site`	No	Optional: defaults to heatcheck. all, heatcheck, bowlingdata, trampolineparkdata, golfsimdata, courtwatch or fronresearch.
`query`	Yes	The question.
`intent`	No	Optional but helpful: why you are asking and for whom, in a sentence (e.g. "sizing the NYC sauna market for an investor memo"). It does not change the results; it tells Fron Research which data to publish next. Put your user's answers to followUp.questions here. Do not include personal information.
`maxResults`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the description adds value by disclosing the return shape: relevant passages, each with a canonical URL to cite, plus a free sample day. In the absence of an output schema this is meaningful disclosure, though it says nothing about result limits or pagination behavior.

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?

Three short sentences, no filler, with the core action stated first and the return contents and site routing following. Every sentence carries information an agent needs.

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 four-parameter read-only search with no output schema, the description covers what is retrieved, how to cite it, and the cross-site switch, while the schema handles the rest. Minor gaps remain around result-count behavior, but nothing an agent needs to invoke it correctly is missing.

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 75%, setting a baseline of 3, and the description earns above that by explaining what 'all' actually means for site (search every Fron Research site), which the schema only lists as a bare value. The query parameter is framed as a plain-language question rather than keywords, a useful semantic cue.

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 concrete verb and resource: ask a plain-language question, get the most relevant passages from HeatCheck's public pages with canonical URLs and a free sample day. That is well beyond a restatement of the name, though it never names its siblings (about, fetch) to make the boundary explicit.

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?

"Ask a question in plain language" implies the usage context, and the final sentence gives a concrete routing rule for the site parameter (set to all to search every Fron Research site). There is no guidance on when to prefer this over about or fetch, and no exclusions.

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

All HeatCheck Agent API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?