Skip to main content
Glama
Sign In
Bevel MCP

Bevel MCP

by JoshPopov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Edit a Bevel food log

bevel_update_food_log
Idempotent

Update servings or time for an existing logged food by ID and date; preview changes with dryRun before enabling writes.

Instructions

Changes the servings and/or time of a logged food (same entry, as the app does). Requires BEVEL_ENABLE_WRITES=true unless dryRun is set.

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": {
      "id": "<id>",
      "date": "<date>"
    },
    "name": "bevel_update_food_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesFood log id from bevel_get_food_logs.
dateYesThe day the food is logged on (YYYY-MM-DD).
timeNoNew local time HH:MM on the same day.
dryRunNo
servingsNoNew number of servings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, idempotent=true, destructive=false), the description adds two things the annotations cannot convey: that the edit is in place on the same entry, and that a write-gating environment flag is required unless dryRun is set. It does not describe what a dryRun response contains or what happens on contradiction (e.g., a time on a different day), which are the remaining behavioral gaps.

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?

Two short sentences, front-loaded with the core mutation scope, then the operational prerequisite. No filler and nothing buried.

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

Completeness3/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 write gate and in-place semantics but says nothing about the return payload or failure modes. Given the partially-undefined dryRun parameter and the open question of partial updates, an agent still has to guess at the edges.

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 80%, so the baseline is met by the schema itself; the description only adds meaning for dryRun by tying it to the write-enable requirement. The schema leaves dryRun's own description empty, and the description does not clarify the interaction between the required date and the optional time, nor confirm that servings/time are optional at least one of which should be given.

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?

"Changes the servings and/or time of a logged food" names a specific verb (changes) and the exact fields under edit, and "(same entry, as the app does)" makes clear this mutates an existing record rather than creating one. That implicitly separates it from bevel_log_food and bevel_delete_food_log, though neither 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?

It states a real prerequisite (BEVEL_ENABLE_WRITES=true unless dryRun is set), which is genuinely useful context. But it never says when to pick this over delete-plus-relog, and it does not state whether at least one of servings/time must be supplied, which the loosely-defined schema leaves ambiguous.

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