Skip to main content
Glama
Sign In
loseit-mcp

loseit-mcp

by cabird
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

describe_food

Get complete nutrition facts and serving sizes for a specific food using its ID from a food search.

Instructions

Get full nutrition detail and serving information for one food, identified by the food_id returned from 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_id": "<food_id>"
    },
    "name": "describe_food"
  }
}

Input Schema

NameRequiredDescriptionDefault
food_idYes32-character hex food ID.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states high-level behavior (get nutrition info) but does not disclose identity, error handling, or safety profile. However, 'describe' implies a read operation, and the output schema likely covers details.

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 sentence, starts with the action verb 'Get', includes the key qualifier 'for one food', and specifies how to obtain the parameter. No fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that an output schema exists (expected to detail nutrition info) and the input is a single well-described parameter, the description provides sufficient information for an agent to use the tool correctly.

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?

Schema coverage is 100%, but the description adds valuable context: the food_id is the one returned by search_food. This goes beyond the schema's static description of '32-character hex food ID' by tying it to a sibling tool's output.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves full nutrition and serving info for one food using a food_id from search_food. It specifies the source of the parameter and distinguishes it from sibling search_food (which returns a list).

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?

Explicitly states that the food_id comes from search_food, indicating the correct workflow. It lacks explicit when-not-to-use or alternative instructions, but the context is clear enough.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools