LobbyStack

List messages

list_messages

Read-onlyIdempotent

Lists messages the receptionist took for the team, newest first: who called, the callback number, urgency, the best time to call back and the message itself. status open means nobody has handled it yet.

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_messages"
  }
}

Input Schema

Name	Required	Description
`limit`	No	How many items to return, 1 to 100. Defaults to 25.
`cursor`	No	The next_cursor value from the previous page. Omit it for the first page.
`status`	No	Only messages with this status.

Output Schema

Name	Required	Description
`data`	Yes
`has_more`	Yes
`next_cursor`	Yes	Pass as cursor to get the next page. Null on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.9/5.0

Behavior4/5

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

The annotations already declare this as a safe, idempotent, non-destructive, closed-world read, so the description's job is to add context — and it does, disclosing sort order ('newest first'), the full set of returned fields, and the operational meaning of the 'open' status. It does not discuss rate limits or result-set emptiness, but against rich annotation coverage this is solid added value.

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 sentences with no filler, and the core identification plus sort order are front-loaded ahead of the status clarification. Every clause carries information the agent can use.

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?

With an output schema present, return values need no explanation, and all three parameters are optional with full schema documentation. The description covers purpose, ordering, and status semantics adequately; only explicit sibling routing is absent, which keeps it short of a 5.

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?

Schema coverage is 100%, so limit and cursor are already fully documented and the baseline would be 3. The description earns an extra point by explaining what 'open' actually means operationally ('nobody has handled it yet'), which the schema's enum description does not convey.

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 gives a specific verb and resource ('Lists messages the receptionist took for the team') and enumerates the returned fields (caller, callback number, urgency, best time to call back, message). It is clearly distinguishable from appointment- or contact-oriented siblings, though it never explicitly contrasts with list_calls, which an agent could plausibly confuse with 'messages'.

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: the tool lists messages, and the note 'status open means nobody has handled it yet' hints at a triage/inbox use case. There is no explicit statement of when to prefer this over list_calls or get_call, nor any prerequisite or exclusion.

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

All LobbyStack tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?