Skip to main content
Glama

Get inbox

get_inbox
Read-onlyIdempotent

Read the user's Habidu Inbox: captured items with no day or time yet, each with id, title, context tag (calls/commute/errands/deep), priority, waiting-for and someday flags. Active items come first, someday items last. Use it before delete_inbox_item (for the id) or to help the user decide what to schedule; scheduled work is in get_tasks. An empty inbox returns count 0. Read-only, takes no parameters.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds behavior beyond that: result ordering (active items first, someday items last) and the empty-inbox edge case returning count 0, which an agent needs to interpret results correctly. It does not discuss result volume or any truncation, but with no parameters there is little more to disclose.

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?

Front-loaded with the resource definition, then field contents, then ordering, then usage routing, then the empty-state note. Every sentence carries distinct information; the field enumeration is long but substitutes for the absent output schema, so it earns its space. Slightly dense as a single run-on block, but 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 must carry return-shape information, and it does: field list, ordering, and the empty case (count 0). Combined with annotations covering safety and a parameterless schema, nothing an agent needs to invoke or interpret this tool is missing.

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?

Zero parameters, so the baseline is 4. The description reinforces this explicitly with "takes no parameters," removing any chance the agent invents a filter argument. No further semantic gain is possible for a parameterless tool.

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 ("Read the user's Habidu Inbox") and immediately defines what an inbox item is: captured items with no day or time yet. It enumerates the returned fields (id, title, context tag, priority, waiting-for, someday) and explicitly separates itself from get_tasks ("scheduled work is in get_tasks"), so an agent can distinguish it from siblings without opening any schema.

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 two concrete use cases (fetching the id before delete_inbox_item, and helping the user decide what to schedule) and names the alternative destination for scheduled work. When-to-use and when-not-to-use are both present, with a named sibling carrying the excluded scope.

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