Skip to main content
Glama

The Front Desk Review

by com.frontdeskreview

Get normalized pricing

get_normalized_pricing
Read-onlyIdempotent

Effective monthly cost per vendor in any theme at a chosen call volume, normalizing flat, per-minute and per-call billing to one comparable number. For non-telephony catalog themes (per-seat / flat plans with no call quota) this returns each plan's base monthly price — the meaningful figure there. Cheapest priceable plan per vendor; quote-only or unpriceable-at-volume vendors return null (never a fabricated figure). avgCallMinutes defaults to 3 and is echoed in assumptions for reproducibility.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionNoTheme slug to query (default "ai-receptionists"). A theme is any of the 271 pricing topics this index covers: the deep hub sections (e.g. ai-receptionists) plus the many catalog topics (e.g. vpn-services, web-hosting, password-managers). Call list_sections or list_coverage for the full slug list — do not assume the old four-section set.
callsPerMonthYes
avgCallMinutesNo

TDQS

A4/5.0
Behavior4/5

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

Annotations already indicate readOnly and idempotent. The description adds that it returns null for unpriceable vendors (never fabricated), defaults avgCallMinutes to 3, and explains behavior per theme type. This provides useful behavioral context beyond annotation hints.

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?

Three sentences, front-loaded with the core purpose, each sentence adds value. No redundant information. Highly concise and well-structured.

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 3 parameters, no output schema, but good annotations, the description covers key behaviors: null handling, default parameter, reproducibility. It could clarify output format more, but overall it provides enough context for correct use.

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 only 33%, but the description adds meaning for section (explains theme slug and default) and avgCallMinutes (default and assumption). However, callsPerMonth lacks description in both schema and description, leaving its format unclear. Partial compensation for low coverage.

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 clearly states the tool computes 'Effective monthly cost per vendor in any theme' by normalizing different billing models. It also distinguishes behavior for telephony vs. non-telephony themes, making the purpose specific and differentiating from sibling tools like compare or find_best.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use (for normalized pricing comparisons) and gives context for different theme types, but it does not explicitly tell when not to use or mention alternatives like compare_products or find_products. Usage is implied but not fully guided.

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

All The Front Desk Review toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation4/5

Tools have distinct purposes, but some overlap exists between 'compare' and 'compare_products' (both do side-by-side comparisons, one for vendors, one for products). However, descriptions clarify the domain difference, and most tools have clear boundaries.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (e.g., list_sections, search_vendors, get_benchmark). No mixed conventions or vague verbs.

Tool Count4/5

19 tools is slightly on the higher side but appropriate for a comprehensive pricing index covering 271 themes. Each tool has a clear role, and the count does not feel bloated.

Completeness5/5

The tool surface covers listing, searching, comparing, finding, detailed info retrieval, and price change tracking. No obvious gaps for the domain of pricing and comparison.

Resources