Trampoline Park Data Agent API

Search Trampoline Park Data

search

Read-only

Ask a question in plain language. Returns the most relevant passages from Trampoline Park Data'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 trampolineparkdata. 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

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description needn't restate safety. The description adds useful behavior beyond annotations: results are public-page passages with canonical URLs for citation and a free sample day, and the site parameter can broaden scope to all Fron Research sites.

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, front-loaded with the core action and return value, then the site-scope option. No unnecessary wording or repetition.

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 search tool with no output schema, the description covers purpose, result format, citation URLs, and the multi-site option. It is nearly complete, though it could say more about how many results are returned or how relevance is determined.

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%, so most parameters are documented in the schema. The description adds meaning about the query being plain language and the site=all option, though it does not explain intent or maxResults further—those are left to schema descriptions and defaults.

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 states a specific verb and resource: ask a plain-language question and receive the most relevant passages from Trampoline Park Data's public pages. It also clarifies the return shape (passages, canonical URL for citation, free sample day) and distinguishes the multi-site mode via the site parameter.

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

Usage Guidelines4/5

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

It clearly indicates when to use this tool—plain-language questions over Trampoline Park Data—and tells the agent to set site to all to search every Fron Research site. It doesn't explicitly contrast with the about or fetch siblings, but the usage context is clear enough for selection.

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

All Trampoline Park Data 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?