Skip to main content
Glama

DietCamera Calorie Dictionary

음식 칼로리 비교

compare_foods
Read-onlyIdempotent

음식 2~10개의 칼로리와 탄수화물·단백질·지방·당류·나트륨을 1회 제공량과 100g(ml) 기준으로 비교합니다(열량 낮은 순). 예: ["짜장면", "짬뽕"], ["빅맥", "와퍼"].

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": {
      "foods": "<foods>"
    },
    "name": "compare_foods"
  }
}

Input Schema

NameRequiredDescriptionDefault
foodsYes음식 이름, foodNumber 또는 페이지 주소 목록

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, not open-world), so the description's job is to add context — and it does, disclosing that results are ordered by ascending calories and that values are presented on two bases. It stops short of describing return shape or handling of unknown food names.

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?

One front-loaded sentence carries the verb, the nutrient set, both bases, and the sort order, followed by two compact concrete examples. Nothing is redundant or padded.

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?

For a one-parameter read-only comparison tool with no output schema, the description supplies enough: what is compared, on what bases, and in what order. The only minor gap is behavior when an input food cannot be resolved.

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 the single 'foods' parameter (name, foodNumber, or page URL) is already documented in the schema. The description reinforces the 2–10 cardinality and shows concrete string-array examples, but adds no format or edge-case detail beyond the schema. Baseline 3 applies.

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 states a specific verb and resource (compare 2–10 foods) and enumerates exactly which nutrients are compared (calories, carbs, protein, fat, sugar, sodium) plus both comparison bases (per serving and per 100g/ml). It does not, however, differentiate itself from siblings like get_nutrition or search_food.

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 by the 2–10 food count and the example pairs (짜장면/짬뽕, 빅맥/와퍼), which make the multi-item comparison scenario obvious. There is no explicit statement of when to prefer this over get_nutrition or search_food, and 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