Skip to main content
Glama

A receptionist vendor's prices, terms and integrations

get_vendor_pricing
Read-onlyIdempotent

One vendor's published plans, overage, cost at 3, 5 and 13 three-minute calls a day, billing terms (rounding, time billed beyond the call, spam, setup fee, contract, trial) and which business tools it writes to, each with the URL and the date it was read. Accepts an id or a name, e.g. "Ruby", "Smith.ai", "Rosie", "RingCentral". Source: ReceptionistPrices.com, prices checked November 17, 2026, https://www.receptionistprices.com/

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": {
      "vendor": "<vendor>"
    },
    "name": "get_vendor_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault
vendorYesVendor id or name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world behavior, so the bar is lower; the description adds genuinely useful context beyond them — data provenance (ReceptionistPrices.com), the freshness date (November 17, 2026), and the fact that each item carries its own source URL and read date. It does not state what happens for an unknown vendor name or whether lookups are fuzzy-matched.

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?

Content is front-loaded and nearly every clause carries distinct payload (pricing, volume scenarios, billing terms, integrations, provenance). The main weakness is that the first sentence is a long enumerated run-on, and the parenthetical billing-terms list is dense; a slightly more broken structure would read faster.

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?

With no output schema available, the description must carry the return-value burden, and it does so thoroughly by listing every category of returned data plus the URL/date metadata. Gaps remain around currency, cost-computation assumptions, and behavior on a vendor that isn't in the index.

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 100% and the single parameter is already documented as 'Vendor id or name', so the baseline is 3. The description adds real meaning by supplying concrete accepted forms (short id-like tokens such as 'Ruby'/'Rosie' alongside full names like 'Smith.ai'/'RingCentral'), which clarifies that either form works and hints at matching style.

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 resource ('One vendor's published plans') and enumerates exactly what is returned: overage pricing, cost at 3/5/13 three-minute calls a day, billing terms (rounding, spam, setup fee, contract, trial), and integration targets with source URLs and read dates. This is specific enough that an agent can distinguish it from list_vendors or integrations without opening the schema.

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 scope 'One vendor's' plus the accepted identifier examples ('Ruby', 'Smith.ai', 'Rosie', 'RingCentral') makes clear this is a single-vendor detail lookup rather than a listing or comparison. It does not explicitly say when to prefer a sibling (e.g., compare_at_volume for multi-vendor cost comparison), so the routing guidance is implicit rather than stated.

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