Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

culvers_menu

List items in one Culver's menu category by slug, returning names, descriptions, images, and nutrition guide links. Get slugs from categories; prices need a selected restaurant.

Instructions

List one Culver's menu category's items. Returns the items in one Culver's menu category, each with name, description, image, and a link to Culver's nutrition guide. Category slugs come from GET /culvers/categories. Prices are not published on the national catalog -- Culver's only prices items once a specific restaurant is selected; see GET /culvers/item for full modifier/topping detail.

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": {
      "category": "<category>"
    },
    "name": "culvers_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYesCategory slug from /culvers/categories

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4.1/5.0
Behavior4/5

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

No annotations, so the description carries the full burden and does well: it discloses the returned fields (name, description, image, nutrition-guide link) and, critically, that prices are not published nationally and only appear once a restaurant is selected. It omits auth/rate-limit context, but the pricing caveat is exactly the kind of non-obvious behavior an agent needs.

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?

Three front-loaded sentences, with the scoping statement first, then return contents, then the important pricing caveat. The first two sentences overlap slightly ('list one category's items' vs 'returns the items in one category'), a minor redundancy in otherwise efficient prose.

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 and no annotations, the description covers the essentials: return fields and the pricing limitation. It is complete enough to call correctly, though it leaves the exact slug format and any pagination/error behavior unstated.

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 coverage is 100% and the schema already documents the single 'category' param as a slug from /culvers/categories. The description restates the same origin for slugs without adding format, casing, or validation detail, so it is a baseline 3.

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 and resource ('List one Culver's menu category's items') and implicitly differentiates from its Culver's siblings by pointing to culvers_categories for slugs and culvers_item for detail. An agent can tell it apart from culvers_item and culvers_categories without opening a 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?

Gives clear routing context: category slugs come from GET /culvers/categories and full modifier detail lives in GET /culvers/item. It establishes the relationship between the sibling tools but does not frame a strict when-to-use/when-not split beyond these pointers.

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