Skip to main content
Glama

DietCamera Calorie Dictionary

프랜차이즈 메뉴 칼로리

franchise_menu
Read-onlyIdempotent

프랜차이즈 브랜드(스타벅스, 맥도날드, 교촌치킨, 배스킨라빈스 등)의 메뉴 칼로리를 정렬해 최대 20개 돌려줍니다. 정렬: kcal_asc(낮은 순, 기본), kcal_desc, protein_desc, sugar_asc, sodium_asc. query 로 메뉴 이름을 좁힐 수 있습니다. 전체 메뉴는 링크된 브랜드 페이지에 있습니다.

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": {
      "brand": "<brand>"
    },
    "name": "franchise_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo
brandYes브랜드 이름. 예: "스타벅스", "BBQ", "맘스터치"
limitNo결과 수(기본 10, 최대 20)
queryNo메뉴 이름 일부. 예: "라떼", "버거"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely new behavioral context: results are capped at 20 and the default ordering is kcal_asc, plus the note that only a subset of the menu is returned. It says nothing about what fields come back or how brands are matched (exact vs. partial name).

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?

Front-loads the core action in the first clause, then lists sort modes compactly, then query behavior, then the subset caveat. Dense and largely waste-free, though the sort enumeration duplicates the schema enum almost verbatim.

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, the description could have named the returned fields (menu name, calories, protein, sugar, sodium), which is a real gap for a ranking tool. Otherwise it is complete for a simple four-parameter read tool: cap, default sort, and query semantics are all covered.

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?

Adds meaning beyond the schema by glossing each sort enum in plain language and flagging kcal_asc as the default, which the schema does not state. It also clarifies that query matches a partial menu name. It does not restate the limit default of 10, which the schema already carries.

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?

States a concrete verb and resource: returns sorted menu calorie data for named franchise brands, with examples (Starbucks, McDonald's, Kyochon, Baskin Robbins) and a hard cap of 20 items. It does not explicitly distinguish itself from siblings like get_nutrition or search_food, so differentiation is left implicit.

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?

Usage is implied rather than stated: this is the tool for calorie-ranked menus from a franchise brand. There is no explicit when-not guidance or named alternative, though the closing note that the full menu lives on the linked brand page hints that results are a truncated subset.

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