Skip to main content
Glama

DietCamera Calorie Dictionary

음식 칼로리 검색

search_food
Read-onlyIdempotent

한국 음식·프랜차이즈 메뉴·가공식품의 칼로리를 이름으로 찾습니다(다이어트카메라 칼로리 사전, 5만여 개). 1회 제공량 기준 열량, 100g(ml)당 열량, 탄수화물·단백질·지방·당류·나트륨과 페이지 링크를 돌려줍니다. 최대 20개. 예: "김치찌개", "스타벅스 라떼", "불닭볶음면".

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": {
      "query": "<query>"
    },
    "name": "search_food"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNofood=일반 음식, franchise=프랜차이즈 메뉴, processed=가공식품
limitNo결과 수(기본 10, 최대 20)
queryYes음식 이름(한글). 브랜드를 붙여도 됩니다. 예: "교촌 허니콤보"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already cover readOnlyHint, idempotentHint, destructiveHint, and openWorldHint, so the safety profile is clear. The description adds useful behavioral detail: the result cap of 20, the dictionary size, and the exact nutrient fields returned. It does not say what happens when a query matches nothing or how matching works, which is a minor gap for a read-only search.

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 compact sentences with the search scope front-loaded, followed by the return fields, the cap, and examples that clarify query form. Almost every clause earns its place. The parenthetical dictionary size is nice-to-have rather than essential.

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?

No output schema exists, so spelling out the returned fields (1회 제공량 열량, 100g당 열량, macros, 페이지 링크) is genuinely valuable and fills that gap. Combined with annotations covering safety, the definition is sufficient to call the tool correctly. Only the lack of routing guidance versus franchise_menu and get_nutrition keeps it from being complete.

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 100%, so an agent already knows how query, kind, and limit are used, including the enum values. The description adds little beyond that: its "최대 20개" repeats the limit maximum in the schema, and the brand-prefix hint with examples only marginally helps with query semantics. The baseline for full coverage is appropriate.

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?

A specific verb ("찾습니다") plus a resource (칼로리) and a stated scope: Korean foods, franchise menus, and processed foods, searched by name, with the data source size (약 5만여 개) and concrete examples. What it covers is unambiguous. It does not differentiate itself from siblings such as franchise_menu or get_nutrition, which is the only missing piece.

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 usage is implied by the name-based search and the examples ("김치찌개", "스타벅스 라떼"), so an agent can infer when to call it. It gives no explicit guidance on when to prefer franchise_menu, get_nutrition, or compare_foods instead, and states no exclusions.

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