Skip to main content
Glama

check_inbox

Fetch new seller replies for all active negotiations, then list what needs action now: reply, follow up, or give up.

Instructions

Fetch new seller replies for all active negotiations and list what needs action now (reply, follow_up, give_up).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses scope (all active negotiations) and the action categories returned, but does not state whether it is purely read-only, whether fetching marks replies as seen, or how the three action labels are decided — meaningful gaps for a tool an agent may poll repeatedly.

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 returned categories parenthesized at the end. No filler, no restatement of the tool name, nothing that could be cut without losing 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?

For a zero-parameter tool with no output schema, the description is close to sufficient: it names the source of data and the shape of the actionable result. It falls short only on return-format specifics and side-effect disclosure, which matter because the caller cannot inspect a schema for them.

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?

The tool takes zero parameters, so the schema leaves nothing to document and the baseline is 4. However, the description adds no parameter-adjacent semantics either (no implicit filters such as time window or negotiation scope), so it neither helps nor harms here; scored at baseline.

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 and resource ("Fetch new seller replies") and scopes it to "all active negotiations," plus a second outcome ("list what needs action now"). That clearly separates it from point-lookup siblings like get_negotiation, but the description never names an alternative, so differentiation is inferential rather than explicit.

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 phrase "list what needs action now (reply, follow_up, give_up)" implies a triage/sweep use case, which is useful implicit guidance. There is no explicit when-to-use or when-not statement and no named alternative (e.g., use get_negotiation for a single thread), leaving the agent to infer boundaries.

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