Skip to main content
Glama

Import food history from another app

trainrec_import_food

Imports past meals from another nutrition app or file: each entry's day, meal, name, numbers PER SERVING and servings. Up to 200 entries per call; the same batch id on later calls makes one import, undone together. Entries already imported from the same app are skipped.

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": {
      "app": "<app>",
      "entries": "<entries>"
    },
    "name": "trainrec_import_food"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYesWhere these came from, e.g. "MyFitnessPal".
batchNoReturned by the first call; pass it on later calls in the same import.
entriesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only give the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false); the description adds real operational context beyond them — a 200-entry batch cap, batch-id grouping so later calls join one import, that the import is undone together, and that already-imported entries from the same app are skipped. It does not cover failure behavior, e.g. whether one invalid entry rejects the whole batch.

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 compact sentences with no filler: the what comes first, then the batching limit, then the dedupe/undo semantics. Every clause carries information an agent needs before calling.

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 mutation tool with no output schema, the description covers the essential mechanics: entry shape, per-serving units, chunking, batch continuation, and dedupe. Missing only what a call returns on success (entry counts, skipped count) and how invalid entries are reported.

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?

With 67% schema coverage, the description still adds meaning the schema does not: it explains that the nutrition numbers are PER SERVING while 'servings' scales the entry, and it explains batch as a continuation key whose reuse merges calls into one undoable import. It also clarifies that 'app' scopes the dedupe check.

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 — importing past meals (with day, meal, name, per-serving numbers, servings) from another nutrition app. This clearly separates it from single-entry logging tools like trainrec_log_food. The phrase 'or file' slightly blurs the line with trainrec_import_file, and no sibling is named explicitly.

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 context is implied well: past meals, bulk, up to 200 entries per call, continue with the same batch id. However, it never says when to prefer this over trainrec_log_food for a single meal or over trainrec_import_file for file-based input, and gives no prerequisites or 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