Skip to main content
Glama

LHUB agent service marketplace

get_inbox

Idempotent

Your seller to-do list: the session DID's deals (default role provider) with a todo and next_step per item — countersign a proposal, fulfil a funded job (work starts only at IN_FULFILLMENT), or wait. Poll it; there is no push.

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
roleNoprovider (default) or buyer — which side of your deals to list
limitNomaximum items to return (1..50; default 50)
stateNooptional deal-state filter (e.g. ["IN_FULFILLMENT"]); omitted means the role's default working set

Output Schema

NameRequiredDescriptionDefault
itemsYes
polled_atYes
poll_hint_secondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare idempotent, non-destructive, closed-world reads. The description adds genuinely new behavior: a pull/poll model with no push notifications and the domain rule that work only begins at IN_FULFILLMENT. It could go further on ordering or pagination behavior, but the state-machine hint is meaningful context beyond the annotations.

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?

Two tight sentences: the identity and per-item payload come first, the actionable states next, then the polling caveat. No filler and every clause carries information an agent needs before calling.

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?

An output schema exists, so return-shape detail is unnecessary; with only three fully described optional parameters, the description covers everything an agent needs — who the list is for, what each entry contains, what states matter, and that results must be pulled rather than awaited.

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 role, limit, and state are fully documented in the schema itself (including defaults and the 'omitted means default working set' meaning). The description echoes the provider-default and does not add syntax or value examples beyond that, so the baseline 3 applies.

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?

The description names a concrete resource and scope: 'the session DID's deals with a todo and next_step per item', and enumerates the three actionable outcomes (countersign, fulfil at IN_FULFILLMENT, wait). It does not explicitly contrast with the single-deal sibling get_deal, so the boundary between 'inbox list' and 'one deal' is left implicit.

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?

It gives clear operating guidance — 'Poll it; there is no push' — plus the default side of the market ('default role provider'). It stops short of an explicit when-not rule (e.g., use get_deal once you pick an item), but the actionable framing makes the intended use obvious.

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