Skip to main content
Glama
Sign In
Bevel MCP

Bevel MCP

by JoshPopov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Set Bevel macro goals

bevel_set_macro_goals
Idempotent

Set daily calorie and macro goals from today, updating same-day goals in place or ending prior goals and starting new ones. Calories default to 4×protein + 4×carbs + 9×fat.

Instructions

Sets daily calorie and macro goals from today on, exactly like the app: if the current goal started before today it is ended yesterday and a new goal starts today; if it already started today it is updated in place. Calories default to 4×protein + 4×carbs + 9×fat. 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": {
      "proteinG": "<proteinG>",
      "carbsG": "<carbsG>",
      "fatG": "<fatG>"
    },
    "name": "bevel_set_macro_goals"
  }
}

Input Schema

NameRequiredDescriptionDefault
fatGYesDaily fat goal in grams.
carbsGYesDaily carbohydrate goal in grams.
dryRunNoIf true, return the exact request without sending it.
caloriesNoDaily calories. Defaults to 4P + 4C + 9F.
proteinGYesDaily protein goal in grams.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare the generic write/idempotent profile; the description adds the actual mutation semantics — the prior goal is ended yesterday and a new one begins today, or an in-place update if it already started today. It also discloses the write-gating requirement and the dryRun escape hatch, which annotations cannot express.

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?

Purpose and scope are front-loaded in the first clause, and the remaining semicolon-separated clauses each carry distinct operational meaning. The only mild redundancy is repeating the calorie formula that the schema already documents.

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 five-parameter mutation tool with no output schema, the description covers the mutation semantics, the default derivation, and the write-enable prerequisite. What is missing is any indication of what a successful call returns or how validation failures surface, though the dryRun parameter partially mitigates that.

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 description coverage is 100%, with every parameter documented including ranges and the calories default. The description restates the 4P+4C+9F default already present in the schema and adds no new syntax, units, or edge-case guidance, so the schema is doing the heavy lifting.

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?

States a specific verb and resource ('Sets daily calorie and macro goals') plus an explicit temporal scope ('from today on'), which cleanly separates it from the read-side sibling bevel_get_macro_goals. An agent can identify the operation without opening the schema.

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?

Gives concrete context for when this applies (goal predating today vs. already starting today) and a prerequisite for invocation ('Requires BEVEL_ENABLE_WRITES=true unless dryRun is set'), which effectively routes the agent to dryRun when writes are disabled. It stops short of naming the read sibling as the alternative for inspecting existing goals.

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