Skip to main content
Glama
Sign In
Cronometer MCP

Cronometer MCP

by ChrisJVanek
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

lookup_barcode

Read-onlyIdempotent

Find packaged foods by entering a UPC/EAN barcode and return matching food records ready for viewing details or adding to a Cronometer diary.

Instructions

Find a packaged food by its UPC/EAN barcode.

Returns matching foods with the same fields as search_foods, so a hit can go straight to get_food_details or add_food_entry.

Args: barcode: The digits printed under the barcode.

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": {
      "barcode": "<barcode>"
    },
    "name": "lookup_barcode"
  }
}

Input Schema

NameRequiredDescriptionDefault
barcodeYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds chaining context (output is field-compatible with search_foods) but says nothing about what happens on a miss, whether multiple foods can match one barcode, or how ambiguous results should be handled.

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?

Front-loaded with the purpose in one line, then a single useful sentence on output compatibility and next steps. The Args block lightly restates the schema but is short and harmless; no filler sentences.

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?

An output schema exists, so return fields need no explanation, and the chaining guidance is the main thing an agent needs. The remaining gap is the zero-match or multi-match case for a lookup tool, which the description does not address.

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 0%, but the description compensates by defining the parameter as the digits printed under the barcode, which rules out passing an image, product name, or URL. It stops short of specifying accepted formats (leading zeros, hyphens, UPC-A vs EAN-13).

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?

"Find a packaged food by its UPC/EAN barcode" gives a specific verb plus resource and implicitly separates it from the text-based search_foods by naming the barcode input. It also names the downstream tools (get_food_details, add_food_entry) so the agent knows where a hit leads.

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?

The barcode framing makes the trigger condition clear (you have a scannable code), and the description states the post-hit path. It does not explicitly say "if you have no barcode, use search_foods," so the alternative routing is left implicit rather than stated.

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