Skip to main content
Glama
Nutrition MCP
by ronkommoji

export_logs

Export profile and food logs as JSON or CSV text, with optional start and end dates to retrieve a specific date range.

Instructions

Export profile and food logs as JSON or CSV text.

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": "export_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNojson
endDateNoOptional YYYY-MM-DD end date.
startDateNoOptional YYYY-MM-DD start date.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and does not say whether this is read-only, whether it returns text or writes a file, whether the whole log history is exported when no dates are given, or how large exports are handled. 'Export' implies retrieval but not the side effects or volume limits an agent needs.

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?

A single front-loaded sentence with no filler. Every word earns its place, and the brevity is appropriate for a simple export call.

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

Completeness2/5

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

There is no output schema and no annotations, so the description should explain the returned payload shape (string vs file), the default no-filter behavior, and date-range semantics. It covers only the surface purpose, leaving the agent to guess at the result.

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 67%: the format enum, its default, and the YYYY-MM-DD date fields are documented in the schema. The description only restates the two output formats and says nothing about the default being JSON, whether the date range is inclusive, or how dates interact with the export scope.

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?

The description names a specific verb ('Export') and specific resources ('profile and food logs') plus output formats, so an agent knows exactly what it produces. It doesn't need to distinguish from siblings, since none of the listed tools export data, but it also never states scope or which logs are included.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus get_daily_status, get_weekly_summary, or search_food_history, and no mention of prerequisites or when exporting is inappropriate. Usage must be inferred entirely from the verb.

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