cronometer-mcp

Overview Schema Source Related Servers Discussions Admin

export_raw_csv

Export unprocessed Cronometer CSV data for any type—servings, daily summaries, exercises, biometrics, or notes. Set start and end dates to pull the exact range you need.

Instructions

Export raw CSV data from Cronometer for any data type.

Useful when you need the full unprocessed export.

Args: export_type: One of 'servings', 'daily_summary', 'exercises', 'biometrics', 'notes'. start_date: Start date as YYYY-MM-DD (defaults to today). end_date: End date as YYYY-MM-DD (defaults to today).

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": {
      "export_type": "<export_type>"
    },
    "name": "export_raw_csv"
  }
}

Input Schema

Name	Required	Description	Default
`end_date`	No
`start_date`	No
`export_type`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.3Mar 21, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations provided, so the description fully carries the burden. It notes 'full unprocessed export' implying no transformation, and describes parameters. However, it does not disclose any potential side effects, what the output looks like, or error conditions. Adequate but not detailed.

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?

The description is short and to the point, with a clear summary sentence, a usage note, and a structured list of parameters. No redundant information, though it could be slightly more compact.

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?

Given the tool has 3 parameters and no annotations, the description covers all parameter semantics well. It does not describe return values, but an output schema is present (though not shown) which likely covers that. The description is sufficient for a simple export tool.

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 description coverage is 0%, so the description must compensate. It lists allowed values for export_type, explains start_date and end_date defaults and format. This adds significant meaning beyond the bare schema properties.

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 'Export raw CSV data from Cronometer for any data type', specifying verb and resource. It also lists valid export types. It distinguishes from sibling tools like get_daily_nutrition which likely return JSON, so purpose is distinct and clear.

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?

The description says 'Useful when you need the full unprocessed export', which gives a usage hint but does not explicitly state when not to use or compare with alternatives like the get_* tools. It lacks explicit when-to-use and when-not-to-use guidance.

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