OrgLines

Log a habit

log_habit

Record (or update) whether the caller completed a habit on a given day. Provide the 'habit_id', an optional 'date' (YYYY-MM-DD, defaults to today) and 'done' (defaults true). Idempotent per habit+date. Only the caller's own habit is reachable. CONFIRMATION: this tool runs immediately when the caller asks for it — it writes only their own record, and they can undo it from this same surface, so the request is taken as the instruction. You get an ordinary result, not a plan_token. Everything destructive, outbound or financial still proposes and waits.

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": {
      "habit_id": "<habit_id>"
    },
    "name": "log_habit"
  }
}

Input Schema

Name	Required	Description	Default
`date`	No
`done`	No
`habit_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations, the description discloses idempotency per habit+date, ownership restrictions, immediate execution semantics, undo availability, and the absence of a plan_token. These are material behavioral details not already present in the annotations or schema.

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 front-loaded with the core operation and parameter defaults, then adds behavioral context. The confirmation paragraph is somewhat long but contains relevant execution semantics rather than filler.

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

Completeness5/5

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

For a simple logging tool with no output schema, the definition covers purpose, parameter behavior, idempotency, ownership, and confirmation semantics thoroughly. An agent has enough information to invoke it correctly without needing additional context.

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?

With 0% schema description coverage, the description supplies useful meaning for all three parameters: habit_id is required, date uses YYYY-MM-DD and defaults to today, and done defaults to true. It does not elaborate on accepted habit_id formats, but the schema already provides the type union.

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 states a specific verb and resource: record or update whether the caller completed a habit on a given day. It also scopes the operation to the caller's own habit, making it clearly distinct from habit-creation or broader logging tools.

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?

It clearly explains the logging use case, including defaults for date and done, and notes idempotency. It does not explicitly name an alternative tool or state when not to use it, but the use context is unambiguous.

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

All OrgLines tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?