Skip to main content
Glama

list_inbox_waiting_requests

Read-onlyIdempotent

List the approved business's oldest unanswered enquiries and booking requests, including requests from the last 90 days.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already establish the safe read-only, idempotent, closed-world profile, so the description's job is to add context — and it does, disclosing the 90-day recency window and an oldest-first emphasis. The phrasing 'oldest unanswered ... including requests from the last 90 days' is mildly ambiguous about whether 90 days is a hard filter or an inclusion clause, and nothing is said about pagination.

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?

A single sentence with no filler, and the resource being listed is front-loaded. The trailing 'including requests from the last 90 days' clause is compact but slightly muddy in meaning, costing a bit of clarity.

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

Completeness3/5

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

For a simple annotated read-only list tool with one optional parameter and no output schema, the description covers what is returned conceptually but leaves the limit/pagination behavior and the exact meaning of the 90-day window unexplained. Adequate, with clear gaps an agent would notice at call time.

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

Parameters2/5

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

There is one parameter (limit) with 0% schema description coverage, so the description carries the full burden — yet it never mentions the limit, its default of 20, or the maximum of 50. An agent gets no guidance on result-size control or whether truncation is possible.

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 specific verb and resource ('List ... unanswered enquiries and booking requests') and adds scope qualifiers ('approved business', 'oldest', 'last 90 days'). It is clearly distinct from sibling read tools like list_appointments or list_contacts, though it never explicitly contrasts itself with any of them.

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?

Usage is only implied: an agent can infer this is for triaging pending enquiries, but there is no statement of when to prefer it over alternatives (e.g. list_appointments) or when it is the wrong choice. No prerequisites or exclusions are given.

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