Microapp

meeting-cost-calculator

Read-onlyIdempotent

Calculate the total cost of a meeting given its duration and a list of attendees with hourly rates. Returns total cost, per-attendee breakdown, cost-per-minute, and order-of-magnitude comparisons (number of $4.50 lattes, number of $800 fully-loaded office days).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`attendees`	Yes	List of attendee rows. At minimum one row. Each row carries a role label, hourly rate, and count — letting you model 'one PM at $90/hr + six engineers at $80/hr' as two rows.
`duration_minutes`	Yes	Meeting length in minutes (e.g. 30 for a half-hour, 60 for an hour, 15 for a standup). Must be greater than zero and at most 1440 (24 hours).

Output Schema

TableJSON Schema

Name	Required	Description
`total_cost`	Yes	Total cost of the meeting in dollars, rounded to cents.
`per_attendee`	Yes	Per-role breakdown — same length as the input attendees array.
`cost_per_hour`	Yes	Sum of (rate × count) across all attendees — the 'burn rate' while the meeting runs.
`cost_per_minute`	Yes	total_cost / duration_minutes, rounded to cents.
`total_attendees`	Yes	Sum of attendee counts across all roles.
`duration_minutes`	Yes	Duration echoed from the input.
`coffees_equivalent`	Yes	total_cost ÷ $4.50 (mid-2025 US average chain latte), rounded down to whole coffees.
`office_days_equivalent`	Yes	total_cost ÷ $800 (fully-loaded daily cost per US knowledge worker), rounded to one decimal place.

Schema Changelog

Changes observed during successful MCP inspections.

AddedMay 21, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds context beyond that by listing the return values (total cost, per-attendee breakdown, cost-per-minute, order-of-magnitude comparisons). No contradiction with annotations.

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?

The description is a single, front-loaded sentence with a parenthetical clarifying output examples. Every phrase earns its place, with no redundancy or filler.

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?

For a simple calculator with a robust output schema and full parameter descriptions, the description adequately covers when to use it and what it returns. No additional context is necessary for correct invocation.

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 the schema already provides rich descriptions for 'duration_minutes' and 'attendees' (e.g., 'fully loaded' explanation, count semantics). The tool description only mentions 'duration' and 'attendees with hourly rates', adding no meaningful detail 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?

The description uses a specific verb ('Calculate') and resource ('total cost of a meeting'), clearly stating inputs and expected outputs. It distinguishes itself from sibling calculators like coffee-habit-cost-calculator or road-trip-cost-calculator by focusing specifically on meetings.

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?

The description implies when to use the tool: when you have a meeting duration and attendees with hourly rates. It does not explicitly name alternatives or exclusions, but the input requirements are clearly stated, making the usage context unambiguous.

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

All Microapp 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?