Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fiveguys_faq

Retrieve Five Guys customer FAQ entries with filtering by category, keyword, and language. Access 142 published questions across 17 categories for quick answers.

Instructions

List Five Guys' published customer FAQ. Returns one page of Five Guys' published customer FAQ corpus -- 142 entries across 17 categories (Menu, Nutritional and Allergens, Ordering, Gift Card, Careers, Franchise, App, Company, The Crew, and others), filterable by category id and free text, in English (default) or Spanish via lang. Get valid category values from GET /fiveguys/faq-categories using the same lang -- category ids are language-specific.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoOptional. Content language: en (default) or es.
pageNoOptional. 1-based page number, default 1.
searchNoOptional. Free-text filter over question and answer text.
categoryNoOptional. Comma-separated faq_category term ids, from GET /fiveguys/faq-categories.
per_pageNoOptional. Entries per page, 1-100, default 20.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / lang / enum
      Added value: +[
+  "en",
+  "es"
+]
  2. Addedv1.16.2

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are present, so the description carries the full burden. It discloses useful behavioral traits: the endpoint returns one page, the corpus contains 142 entries across 17 categories, filtering is supported, English is the default language, and category IDs are language-specific. It stops short of describing the returned entry fields or pagination metadata, which prevents a 5.

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?

Two dense sentences with zero filler. The core action and resource are front-loaded, followed by corpus stats, filter options, language behavior, and the prerequisite category endpoint. Every clause earns its place.

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?

Despite having no output schema and no annotations, the description covers endpoint purpose, filtering, pagination, language, and the dependency on the FAQ-categories endpoint. The main gap is that it does not describe the shape of an individual FAQ entry, though the search parameter hints at question and answer fields.

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?

With 100% schema coverage the baseline is 3, but the description adds non-obvious meaning beyond the schema: category IDs are language-specific and must be fetched using the same lang value. It also summarizes the free-text and category filter behavior, reinforcing the relationship between parameters.

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?

States a specific verb ('List') and resource ('Five Guys' published customer FAQ'). It further distinguishes itself from the sibling fiveguys_faq_categories by pointing to that endpoint for category values, and from other Five Guys tools like menu/nutrition by clearly scoping the corpus.

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?

Clearly establishes when to use this tool: to list FAQ entries, optionally filtered by category or free text and localized via lang. It also routes the agent to GET /fiveguys/faq-categories for valid category values, which is an effective reference to the companion sibling, though it does not explicitly state exclusions or when-prefer-alternative conditions.

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

Deploy Server

Other Tools