Skip to main content
Glama

Price summary for a service

get_price_summary
Read-onlyIdempotent

One service's price. What New York area vendors in one category publish as a starting price for a whole event: the median and the middle half (25th to 75th percentile), from how many vendors and when, optionally for one area, plus per-hour or per-guest figures where the category is priced that way. Comes with a one-sentence summary and the page to cite. Use it to answer "how much does a wedding DJ cost in Brooklyn".

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": {
      "category": "<category>"
    },
    "name": "get_price_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoOptional area: NYC (any of the five boroughs), Manhattan, Brooklyn, Queens, Bronx, Staten Island, Long Island, Westchester, North Jersey or Central Jersey, or New Jersey for both; a county or town also works (Bergen County, Hoboken, Monmouth County). Omit for the whole New York area.
categoryYesVendor category in plain words: "photographers", "DJ", "caterer", "florist", "planner", "live band", "videographer", "photo booth", "hair and makeup" or "cakes". list_categories gives the full list.

Output Schema

NameRequiredDescriptionDefault
areaNo
unitNo
as_ofNo
medianYes
sourceYes
cite_asNoAgent Bookability Index by The Runup (index.therunup.ai)
vendorsYesHow many vendors' published prices the figures come from.
categoryYes
per_unitNo
sentenceYesOne sentence that states the figures with their source.
area_noteNoSet when the area had too few prices and the whole region is used.
cost_pagesNoMore specific index pages answering what this costs (wedding, per hour, per guest), each with a one-sentence summary.
low_quartileYes
high_quartileYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / cost_pages / description
      Previous value: -"More specific index pages answering what this costs (wedding, per hour, per guest), each with its quotable answer."New value: +"More specific index pages answering what this costs (wedding, per hour, per guest), each with a one-sentence summary."
    • changedOutput schema / properties / sentence / description
      Previous value: -"One sentence with the figures, made to be quoted whole."New value: +"One sentence that states the figures with their source."
  2. Changed1 schema field changed
    • changedInput schema / properties / area / description
      Previous value: -"Optional area: NYC (any of the five boroughs), Manhattan, Brooklyn, Queens, Bronx, Staten Island, Long Island, Westchester, North Jersey or Central Jersey. Omit for the whole New York area."New value: +"Optional area: NYC (any of the five boroughs), Manhattan, Brooklyn, Queens, Bronx, Staten Island, Long Island, Westchester, North Jersey or Central Jersey, or New Jersey for both; a county or town also works (Bergen County, Hoboken, Monmouth County). Omit for the whole New York area."
  3. Changed1 schema field changed
    • addedOutput schema / properties / cost_pages
      Added value: +{
      +  "description": "More specific index pages answering what this costs (wedding, per hour, per guest), each with its quotable answer.",
      +  "items": {
      +    "additionalProperties": {
      +      "type": "string"
      +    },
      +    "type": "object"
      +  },
      +  "title": "Cost Pages",
      +  "type": "array"
      +}
  4. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value beyond that: the statistical shape of the answer (median and middle half), the provenance signals (how many vendors, when), the per-hour/per-guest variants, and that a citable page and one-sentence summary accompany the figures.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded in the first sentence and each subsequent sentence adds a distinct fact (statistics, sample size, optional area, derived figures, citation). It is a dense single block rather than a bulleted structure, but there is little outright waste.

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?

With an output schema present, full parameter documentation, and complete annotations, the description only needs to establish scope and intent — which it does, including geography, aggregation basis and intended question type. 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.

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 already carry detailed documentation, including the full area vocabulary and example categories. The description only restates that results are scoped to one category and optionally one area, adding no syntax or semantics the schema lacks.

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?

The description names the resource precisely — one service category's aggregate price statistics (median, 25th-75th percentile, vendor count, time window) for the New York area. An agent can tell this is an aggregate market-price tool, distinct in kind from the vendor-level siblings like get_vendor or search_vendors, though no sibling is named explicitly.

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 gives a concrete use case in the form of an example question ("how much does a wedding DJ cost in Brooklyn") and states the optional-area behavior ("optionally for one area"). It stops short of naming alternatives such as compare_vendors or when *not* to use this tool.

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.

Resources