Skip to main content
Glama

DietCamera Calorie Dictionary

음식 영양성분

get_nutrition
Read-onlyIdempotent

음식 하나의 영양성분표(열량·탄수화물·당류·식이섬유·단백질·지방·포화지방·트랜스지방·콜레스테롤·나트륨)를 1회 제공량과 100g(ml) 기준으로, 1일 기준치 대비 %와 함께 돌려줍니다. 음식 이름, foodNumber, 또는 search_food 가 준 페이지 주소를 넣습니다.

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": {
      "food": "<food>"
    },
    "name": "get_nutrition"
  }
}

Input Schema

NameRequiredDescriptionDefault
foodYes음식 이름, foodNumber, 또는 https://dietcamera.doinglab.com/food/... 주소

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 readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so safety is covered. The description adds genuinely useful behavior not in the annotations: results are reported on both a per-serving and per-100g(ml) basis with % of daily reference values. It says nothing about what happens when a name is ambiguous or unmatched, which is the remaining behavioral gap.

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?

Two sentences, front-loaded with the return contents before the input forms. The long nutrient parenthetical earns its space because there is no output schema, though the second sentence nearly duplicates the schema's parameter text.

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 correctly carries the burden of explaining the return shape (nutrients, dual basis, %DV) and the accepted input forms. A note on handling ambiguous or missing foods is the only notable omission for this simple lookup tool.

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?

With one parameter at 100% schema coverage, the baseline is 3. The description largely restates the schema's own food parameter documentation, adding only the provenance hint that the URL can come from search_food.

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 specific verb and resource ('음식 하나의 영양성분표...를 돌려줍니다') and enumerates the exact nutrient fields returned. Scoping to a single food implicitly separates it from compare_foods, but no sibling is named explicitly, so it stops short of full differentiation.

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 call context by listing the three acceptable input forms, including chaining from search_food's page URL. It does not state when to prefer compare_foods or franchise_menu instead, so there are no explicit 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