Skip to main content
Glama

Budget for an event

estimate_event_budget
Read-onlyIdempotent

Several services together. The published starting prices of a whole event's vendors: for each service, the low, median and high published starting price in the area, worked out for the guests and hours given, and the sum. Use it to answer "what will a DJ, photographer and caterer cost for a 120-guest bar mitzvah in Brooklyn". For one service in detail use get_price_summary; for actual vendors use shortlist_vendors.

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": {
      "categories": "<categories>"
    },
    "name": "estimate_event_budget"
  }
}

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.
hoursNoLength of the event in hours. Where a service has per-hour prices, they are worked out for this long.
guestsNoNumber of guests. Catering and cakes, usually priced per guest, are worked out for this many.
categoriesYesThe services the event needs, in plain words, e.g. ["DJ", "photographer", "caterer", "cake"]. Up to 8.

Output Schema

NameRequiredDescriptionDefault
areaYes
as_ofNo
hoursYes
notesNo
guestsYes
cite_asNoAgent Bookability Index by The Runup (index.therunup.ai)
sentenceYesOne sentence that states the total with its source.
servicesYes
total_low_usdYesSum of each service's 25th percentile: a rough low end, not a quote.
total_high_usdYesSum of each service's 75th percentile: a rough high end.
total_median_usdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / sentence / description
      Previous value: -"One sentence with the total, made to be quoted whole."New value: +"One sentence that states the total with its source."
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description only needs to add semantics. It does: the numbers are 'published starting prices' rather than quotes, they are adjusted for the guests and hours supplied, and a sum is returned. It says nothing about coverage gaps (services with no data) or pricing recency, which keeps it short of a 5.

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 output shape is front-loaded and the routing sentence closes it cleanly with no filler. The opening fragment "Several services together." is awkward and nearly meaningless on its own, which is the only real blemish.

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 four parameters, full schema coverage, annotations and an output schema, an agent needs only purpose, output meaning, and sibling routing. The description supplies all three and explicitly frames the result as starting-price estimates rather than vendor quotes.

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%, including the area enumeration and the per-guest/per-hour semantics of guests and hours, so the schema does the heavy lifting. The description only restates that values are 'worked out for the guests and hours given' and that categories are plain-word services (up to 8), adding little beyond the schema. Baseline 3 is appropriate.

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 and resource: it returns, per service, the low/median/high published starting price for an area plus the sum for a multi-service event. It is immediately distinguishable from get_price_summary (single service) and shortlist_vendors (actual vendors), so an agent can route without opening a schema.

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?

It gives a concrete triggering question ("what will a DJ, photographer and caterer cost for a 120-guest bar mitzvah in Brooklyn") and names both alternatives with the condition that selects each: get_price_summary for one service in detail, shortlist_vendors for actual vendors. When-to-use and when-not-to-use are both explicit.

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