Skip to main content
Glama

List the AI and virtual receptionists in the price index

list_vendors
Read-onlyIdempotent

Every AI receptionist, virtual receptionist and build-your-own voice AI platform ReceptionistPrices.com prices, with its entry plan, whether it publishes prices, and the date its pricing page was read. Use it to find a vendor's id. Source: ReceptionistPrices.com, prices checked November 17, 2026, https://www.receptionistprices.com/pricing/

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

Input Schema

NameRequiredDescriptionDefault
typeNoai: AI receptionists; virtual: live people (and live plus AI); platform: build your ownall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by stating source provenance, the pricing-check date, and that the list is comprehensive, though it does not discuss result ordering or any pagination behavior.

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 definition is compact and front-loaded: the first sentence establishes scope and returned fields, and the second supplies provenance and freshness. No sentence is wasted, and the source URL is useful rather than filler.

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?

For a one-parameter, read-only list tool with no output schema, the description is nearly complete: it says what is listed, which fields are returned, where the data comes from, and how fresh it is. The only minor gap is that it does not describe result ordering or whether the full list is always returned.

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 single type parameter is already fully documented in the schema with enum meanings. The description does not add further parameter semantics beyond what the schema provides, so the baseline score 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 states a specific verb and resource: it lists every AI receptionist, virtual receptionist, and build-your-own voice AI platform priced by ReceptionistPrices.com. It also names the exact fields returned, including entry plan, pricing publication status, and pricing-page read date, which clearly differentiates it from siblings such as get_vendor_pricing.

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 explicitly says to use it to find a vendor's id, which gives the agent a concrete routing purpose relative to vendor-detail tools. It does not spell out when not to use it or name an alternative, so it stops short of the highest level of guidance.

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