Skip to main content
Glama
Schimmilab

things3-mcp-server

by Schimmilab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_inbox

List all unfiled to-dos in Things 3 Inbox. Supports optional tag filtering to locate and triage specific tasks.

Instructions

List all to-dos currently in the Things 3 "Inbox" (unfiled tasks).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoOnly return to-dos carrying ANY of these tags (comma-separated, case-insensitive). Empty = no tag filter.
limitNoReturn at most N to-dos (0 = all). Applied AFTER the tag filter.
include_notesNoFalse drops the `notes` field — notes dominate the payload.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.3.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / include_notes
      Added value: +{
+  "default": true,
+  "description": "False drops the `notes` field — notes dominate the payload.",
+  "type": "boolean"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 0,
+  "description": "Return at most N to-dos (0 = all). Applied AFTER the tag filter.",
+  "type": "integer"
+}
    • addedInput schema / properties / tag
      Added value: +{
+  "default": "",
+  "description": "Only return to-dos carrying ANY of these tags (comma-separated,\ncase-insensitive). Empty = no tag filter.",
+  "type": "string"
+}
    • removedInput schema / title
      Removed value: -"get_inboxArguments"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"get_inboxOutput"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  2. First observedv0.2.1

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It adds the meaningful 'unfiled tasks' semantic but does not state whether this is a purely read-only operation, how results are ordered, whether pagination occurs, or what happens when no to-dos are present. The description communicates the purpose but not the behavior.

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?

The description is a single, tightly-crafted sentence that front-loads the verb and object and includes a useful parenthetical explanation. There is no fluff, repetition, or extraneous information.

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?

Given the simple interface with three optional, self-documented parameters and an existing output schema, the brief description is almost sufficient. It clearly identifies the resource and scope, but it could be slightly more complete by explicitly positioning itself against count of siblings such as list_todos and search_todos.

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%, and all parameters (tag, limit, include_notes) are thoroughly described in the input schema. The tool description contributes no additional parameter-level meaning, so the schema is doing the heavy lifting. This meets the baseline for high schema coverage.

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 uses a specific verb ('List'), a precise resource ('all to-dos currently in the Things 3 Inbox'), and a clarifying parenthetical ('unfiled tasks') that distinguishes it from siblings like get_today, get_completed, and list_todos. It clearly identifies what the tool does and where its scope lies.

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 scoping phrase 'currently in the Inbox' implies when this tool should be used: whenever an agent needs unfiled or Inbox to-dos. However, it never explicitly names alternatives or defines when not to use it, leaving the selection guidance an unspecified baseline.

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