Skip to main content
Glama
Sign In
bookmarks

bookmarks

by jgharbieh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

inbox

Lists items the user dropped in a designated folder for the agent to process, creating that folder automatically if it is missing.

Instructions

List what the user dropped in the Inbox folder for you to process (creates the folder if missing).

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

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose one genuinely non-obvious trait — the tool creates the folder if missing, i.e. a write side effect on a listing operation — but says nothing about permissions, idempotency, or ordering. Return shape is covered by the output schema, so that omission is acceptable.

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?

A single sentence with the primary action front-loaded and the side effect tucked into a parenthetical. Every clause earns its place.

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 zero-parameter tool with an output schema, the description covers purpose and the one surprising side effect, which is enough to call it safely. The only gap is routing relative to siblings that also enumerate content.

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?

The tool takes zero parameters, so there is no parameter semantics to document; baseline 4 applies. Nothing in the description misrepresents the argument surface.

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 ('List') and a specific resource ('the Inbox folder'), and adds scope with 'what the user dropped in ... for you to process'. It is clear what the tool returns, but it does not distinguish itself from list-adjacent siblings such as tree, search, or read_this.

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?

'for you to process' implies a workflow context (inbox triage), which is useful implied guidance. However, there is no explicit when-to-use vs when-not-to-use statement and no named alternative among the many siblings that also surface items.

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