better-bear

Overview Schema Source Related Servers Discussions Admin

bear_get_todos

Read-onlyIdempotent

Retrieve all TODO items from a Bear note, including text, completion status, and index for toggling completion.

Instructions

Get all TODO items from a specific Bear note. Returns each item's text, completion status, and index number (use the index with bear_toggle_todo to toggle items).

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>"
    },
    "name": "bear_get_todos"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Note ID (uniqueIdentifier)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.19Apr 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. Description adds value by detailing return fields (text, completion status, index), which aids agent expectations.

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 concise sentences: first states purpose, second details return and usage. No filler, every word contributes.

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 simple read tool with one parameter, the description fully covers purpose, return structure, and usage hint. Lack of output schema is compensated by describing return fields.

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?

With 100% schema description coverage, the description reinforces the parameter's meaning (note ID) but does not add novel semantics beyond 'specific Bear note'.

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 verb 'Get' and resource 'all TODO items from a specific Bear note' clearly specify the action and scope. It distinguishes from siblings like bear_list_todos (likely cross-note) and bear_toggle_todo (toggle action).

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?

Explicitly mentions using the returned index with bear_toggle_todo, guiding the agent on how to chain tools. Does not discuss when not to use (e.g., for cross-note todos), but provides clear context.

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