Skip to main content
Glama

DietCamera Calorie Dictionary

이달의 프랜차이즈 신메뉴 칼로리

new_menus
Read-onlyIdempotent

프랜차이즈가 그달에 공식 영양정보를 새로 올린 신메뉴의 칼로리를 낮은 순으로 최대 20개 돌려줍니다. month(YYYY-MM)를 비우면 가장 최근 달입니다. brand 로 좁힐 수 있습니다.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "new_menus"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandNo브랜드 이름으로 좁히기. 예: "파리바게뜨"
limitNo결과 수(기본 20, 최대 20)
monthNoYYYY-MM. 비우면 가장 최근 달

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 declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely non-structured traits: ascending calorie ordering, a hard 20-result ceiling, and default-month fallback semantics. It does not describe what fields come back per item, which is the remaining gap.

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?

Three short sentences, front-loaded with purpose and result shape, then default and filter behavior. No filler, no repetition, nothing an agent must skip over.

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 does carry return-shape duty and delivers ordering, cap, and the calorie focus. It omits the per-item fields (e.g., brand, menu name, date) and whether results are empty when no franchise posted new nutrition data, which are the only meaningful omissions for a 3-parameter read 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?

Schema coverage is 100% and the schema already documents brand, limit bounds, and the YYYY-MM default, so the description largely restates it. The only added nuance is confirming the 20-item output ceiling, which is marginal beyond the schema's 'maximum 20'.

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 (returns calories of newly posted franchise menus) plus the qualifying condition ('그달에 공식 영양정보를 새로 올린'), sort order, and a 20-item cap. It is clearly distinguishable from a general menu or nutrition lookup, though it never names the sibling tools it differs from.

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?

Gives concrete defaults ('month를 비우면 가장 최근 달') and an optional narrowing path via brand, which is usable guidance. It stops short of saying when to prefer this over franchise_menu or get_nutrition, so the agent must infer the alternative from the 'new this month' framing.

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