Skip to main content
Glama

KanbanMCP

Read your inbox

inbox
Idempotent

Reads what waits for you: answers to your questions, and comments that @mention you or your personas. Marks both as seen. Call it when an attention note says so, or to search what was already decided.

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": "inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNoInclude mentions you have already seen.
daysNoOnly answers and mentions from the last N days.
mineNoOnly answers to what you raised or the cards you hold.
limitNoHow many answers and mentions to return.
queryNoWords that must appear in the question or the answer.
sinceNoOnly answers after this time (milliseconds).
boardIdNoBoard id or slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations only state readOnlyHint=false and idempotentHint=true; the description supplies the missing reason — 'Marks both as seen' — which is the key mutation an agent must know about. This is genuine added value beyond the structured hints. It does not disclose permissions, rate limits, or return shape, so not a 5.

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?

Two short sentences, front-loaded with what the tool returns and immediately following with the side effect and invocation triggers. Nothing is padded, though the phrasing is slightly narrative where a crisper clause could carry the same content.

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 7-parameter, no-required-argument tool with no output schema, the description covers the core behavior (what it returns and that it marks items seen) and its triggers. It omits any sense of result size/limit behavior and return ordering, which leaves a small gap for an agent relying on the response.

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 coverage is 100%, so every parameter is already documented in the schema. The description's mention of answers/mentions loosely maps to the query and mine semantics but adds no syntax, format, or default guidance. Baseline 3 applies when the schema does the heavy lifting.

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

Purpose4/5

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

States a specific verb (reads) and the exact resource contents: answers to your questions and comments that @mention you or your personas. This is more specific than the title and lets an agent distinguish it from siblings like comment or show. It stops short of explicitly differentiating from other retrieval tools such as find_cards or events_since.

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?

Gives two concrete triggers: 'Call it when an attention note says so' and 'to search what was already decided.' That is clear usage context without naming a competing alternative tool, so it falls short of the explicit when/when-not/alternative framing of a 5.

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