Skip to main content
Glama

Create an inbox item

create_inbox_item

Capture ONE to-do with NO date or time into the user's Habidu Inbox: an idea, an errand, a call, or something they are waiting on. Use create_task instead when the user gives a day or a time. Returns {id, title, ...}. If the same item is already in the Inbox it is updated in place and the result carries merged:true - tell the user it was updated, not added. ok:false means nothing was saved. Not preview-gated.

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": {
      "title": "<title>"
    },
    "name": "create_inbox_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesShort title of the to-do, no time, e.g. "Buy stamps".
categoryNoBest-fit category for this item. Infer from the built-ins (Work, Personal, Health, Learning, Creative, Errands). You may also use one of the user's OWN custom categories when they name it. Never invent a new category name while merely inferring. Omit if unclear.
priorityNoPriority: 4 Very High, 3 High, 2 Medium, 1 Low. Set ONLY when the user expresses importance/urgency. Omit otherwise.
waiting_onNoGTD Waiting For: WHO or WHAT the user is waiting on ("Tejas", "the plumber's quote"). Set when the user says they are waiting on someone else for this item - it then lives in the Inbox's ⏳ Waiting For section instead of the normal list.
follow_up_dateNoOnly with waiting_on: the day (YYYY-MM-DD) the user wants to follow up if still waiting.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare the generic safety profile (readOnly=false, destructive=false, idempotent=false, openWorld=false), while the description adds behavior the agent could not otherwise know: duplicate items are merged in place and flagged merged:true, the agent must tell the user 'updated, not added', ok:false means nothing was saved, and the call is not preview-gated. The merge-on-duplicate behavior sits in mild tension with idempotentHint=false, but since 'updated in place' is not the same as repeated identical calls being no-ops, this is not a genuine contradiction.

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?

Five short sentences, each carrying distinct information: purpose, sibling routing, return shape, dedup semantics, and failure signal. The scoping constraint is front-loaded in the first clause and there is no 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?

There is no output schema, so the description takes on the return contract and does so adequately: '{id, title, ...}', the merged:true flag, and ok:false as the failure indicator. Combined with the 100%-covered input schema, an agent has everything needed to call and interpret the result.

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%, so every parameter is already documented in detail, including the built-in category list, the priority scale, and the waiting_on/follow_up_date pairing. The description adds essentially nothing parameter-specific beyond repeating the 'no date or time' rule that the title schema already states, so the baseline 3 applies.

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 ('Capture ONE to-do ... into the user's Habidu Inbox') plus concrete examples of what qualifies (an idea, an errand, a call, something they are waiting on). It also names the boundary condition that separates it from the sibling create_task: no date or time.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit routing rule with the alternative named: 'Use create_task instead when the user gives a day or a time.' The positive case is equally explicit, and the 'no date or time' constraint appears in both the purpose and the title guidance, so there is no inference required.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources