Skip to main content
Glama

get-inbox

Retrieve tasks from your Things 3 inbox to view pending items and manage your workflow. Specify detail level and limit results for focused task review.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
detailNoResponse detail level. Defaults to compact.
limitNoMaximum number of todos to return

Implementation Reference

  • The "get-inbox" tool registration and handler implementation. It uses `getInboxTodos` helper to fetch inbox tasks from the database and `toTaskView` to format them.
      "get-inbox",
      {
        detail: z.enum(["compact", "full"]).optional().describe("Response detail level. Defaults to compact."),
        limit: z.number().int().positive().optional().describe("Maximum number of todos to return"),
      },
      async ({ detail, limit }) => {
        const requestedDetail = detail ?? "compact";
        const todos = await withDatabase((db) =>
          applyLimit(getInboxTodos(getAllTasks(db)), limit).map((task) =>
            toTaskView(task, requestedDetail)
          )
        );
        return buildTextResponse(`Found ${todos.length} inbox todos`, {
          todos,
          detail: requestedDetail,
          limit: limit ?? null,
        });
      }
    );
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/soycanopa/SupaThings-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server