Skip to main content
Glama
Sign In

ScareMap

by app.scaremap
OverviewDiscussionsAdmin

Get one haunt with reviews

scaremap_get_haunt
Read-onlyIdempotent

Get the full record for one haunt: description, category, season, location, average ratings, and up to 20 of the newest visitor reviews (stars, scare, text, date). Call this after scaremap_find_haunts or scaremap_find_haunts_in_city when the user wants detail on a specific result. Pass the slug from those results, or the haunt id. Reviews are anonymous. A haunt with no reviews returns an empty list.

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": "scaremap_get_haunt"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoHaunt UUID. Use instead of slug.
slugNoHaunt slug from other ScareMap tools, for example "hellscream-haunted-house".

Output Schema

NameRequiredDescriptionDefault
hauntYes
reviewsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world traits, so the bar is lower. The description still adds real behavioral context: reviews are capped at 20 newest, reviews are anonymous, and a haunt with no reviews returns an empty list rather than erroring. It does not mention failure behavior for a bad slug/id.

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?

Four tight sentences: return contents first, then usage trigger, then input sourcing, then edge-case behavior. Nothing is redundant and the most decision-relevant information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, yet the description still previews the payload and the 20-review cap. Combined with full annotation coverage and a fully described 2-param schema, an agent has everything needed to call this 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% and both parameters are documented in-schema, so the baseline is 3. The description only adds that either the slug or the haunt id may be passed and that the slug originates from sibling tool results, which is marginal value beyond the schema.

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?

States a specific verb (Get) and resource (one haunt) plus the exact fields returned: description, category, season, location, average ratings, and newest reviews. This clearly separates it from the sibling find/list tools, which return multiple haunts rather than a single full record.

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

Usage Guidelines5/5

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

Explicitly says to call it 'after scaremap_find_haunts or scaremap_find_haunts_in_city when the user wants detail on a specific result,' naming both alternatives and the condition that selects this tool. It also tells the agent where the required input comes from ('Pass the slug from those results').

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

All ScareMap toolsInspect
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