Skip to main content
Glama
Sign In

The Front Desk Review

by com.frontdeskreview
OverviewDiscussionsAdmin

Find best (ranked)

find_best
Read-onlyIdempotent

For 'best for ' and 'cheapest ': returns the theme's vendors ranked by entry price (cheapest first, quote-only last), each with its verified compliance facts (HIPAA/SOC 2/GDPR), free-tier flag, best-for tags, the entry plan's source and its citation (figure, plan, source page, read date and record URL in one line). Conjunctive fact filters narrow it to what this index has actually CONFIRMED — requireHipaa / requireSoc2 / requireGdpr / requireFreeTier (e.g. 'best CRM for HIPAA' = section 'crm-software' + requireHipaa:true). Omit all filters to rank the whole theme by price. Set section to the theme slug from list_sections. Never infers a fact it has not verified.

Input Schema

NameRequiredDescriptionDefault
sectionNoTheme slug to query (default "ai-receptionists"). A theme is any of the 275 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). list_sections and list_coverage return the full slug list.
requireGdprNoOnly vendors with confirmed GDPR compliance.
requireSoc2NoOnly vendors with a confirmed SOC 2 attestation.
requireHipaaNoOnly vendors with confirmed HIPAA support (a BAA).
requireFreeTierNoOnly vendors with a genuine $0 forever plan.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / section / description
      Previous value: -"Theme slug to query (default \"ai-receptionists\"). A theme is any of the 275 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."New value: +"Theme slug to query (default \"ai-receptionists\"). A theme is any of the 275 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). list_sections and list_coverage return the full slug list."
  2. Changed1 schema field changed
    • changedInput schema / properties / section / description
      Previous value: -"Theme slug to query (default \"ai-receptionists\"). A theme is any of the 273 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."New value: +"Theme slug to query (default \"ai-receptionists\"). A theme is any of the 275 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."
  3. Changed1 schema field changed
    • changedInput schema / properties / section / description
      Previous value: -"Theme 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."New value: +"Theme slug to query (default \"ai-receptionists\"). A theme is any of the 273 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."
  4. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses ranking order (cheapest first, quote-only last), returned fields, verified compliance facts, free-tier flags, citation content, and the key constraint that it never infers unverified facts. This is substantial behavioral context.

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 description is front-loaded with the use case and return behavior, and every sentence contributes. It is dense in a single paragraph, but not padded or redundant.

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 no output schema, the description carries the return-value burden and does so by naming ranked vendors, compliance facts, free-tier flag, best-for tags, and citation components. It is complete enough for an agent to understand what calling the tool yields.

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%, so the baseline is 3, but the description adds meaningful semantics: filters are conjunctive, they only narrow to confirmed facts, and it gives a concrete requireHipaa example tied to section. It also clarifies section usage via list_sections.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 a theme's vendors ranked by entry price, with compliance facts and citation details. It is clear what the tool does, but it does not explicitly distinguish itself from several siblings such as compare or search_vendors.

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?

It states the query patterns it serves ('best <theme> for <use case>' and 'cheapest <theme>') and explains that omitting filters ranks the whole theme by price. It points to list_sections for the section slug, but does not explicitly say when to use a sibling tool instead.

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
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