Skip to main content
Glama
Sign In
Bevel MCP

Bevel MCP

by JoshPopov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Clear a Boolean Journal factor

bevel_clear_journal_boolean
Idempotent

Clears a yes/no Journal factor for one day so it appears unanswered; supports dry-run preview and requires writes enabled.

Instructions

Clears a yes/no Journal factor for one day, so it shows as not answered — exactly what the app sends: the same entry with isNotSet: true and no boolValue. Does nothing if there is no entry or it is already cleared. 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": {
      "factorKey": "<factorKey>"
    },
    "name": "bevel_clear_journal_boolean"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoCalendar day YYYY-MM-DD in the configured time zone. Defaults to today.
dryRunNoIf true, return the exact request that would be sent without sending it.
factorKeyYesPreset factor key of the entry to clear.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the write gate and env-flag requirement, the silent no-op when there is nothing to clear, and the exact resulting record shape. That is useful behavioral context, though there is mild tension between "clears" a stored entry and destructiveHint=false that is not addressed.

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?

Three short sentences, front-loaded with the action and outcome, then the no-op caveat, then the precondition. Every sentence carries distinct information and nothing is padded.

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 three-parameter idempotent mutation with annotations covering safety and idempotency and no output schema, the definition covers outcome, no-op behavior, and auth gating. Only the return payload for a non-dryRun call is left unstated.

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 100%, with date, dryRun, and factorKey already documented in the schema, so the baseline is 3. The description only lightly reinforces this ("for one day", the dryRun preview) and adds no format or default details beyond what the schema states.

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?

"Clears a yes/no Journal factor for one day" gives a precise verb, resource, and scope, and the added payload note (isNotSet: true, no boolValue) makes the result concrete. It does not name bevel_set_journal_boolean as the counterpart, so the clear-vs-set distinction is left to be inferred from the verb rather than stated.

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 supplies a real prerequisite (BEVEL_ENABLE_WRITES=true unless dryRun is set) and a no-op condition (no entry or already cleared), which an agent needs before calling. However, it never says when to reach for this instead of the sibling set tool or journal-read tools, so selection guidance is only implied by the verb.

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