Skip to main content
Glama
Anou4r

superchat

by Anou4r
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

superchat_list_inboxes

Read-onlyIdempotent

List a page of inboxes that organize conversations and provide IDs for routing messages. Use after or before cursors to navigate paginated results.

Instructions

List one page of inboxes that organize conversations in this workspace. Use inbox IDs when routing a conversation. Use after or before to continue from a previous page; each call returns only one page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoFetch the page after this cursor; pass pagination.next_cursor from a previous result.
limitNoNumber of records in this page, from 1 to 100. Defaults to 25; the tool never fetches later pages automatically.
beforeNoFetch the page before this cursor; pass pagination.previous_cursor from a previous result. Cannot be combined with after.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds useful behavioral context: pagination is manual, only one page is returned per call, and inboxes are workspace-scoped. No contradiction with 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?

Three short sentences with no filler: purpose first, then downstream use, then pagination behavior. Every sentence 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 simple read-only list tool with full schema coverage and rich annotations, the description covers scope, pagination, and one-page behavior. It doesn't describe the inbox object shape, but no output schema exists and the description is sufficient for correct invocation.

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 description coverage is 100%, so the schema already documents after, before, and limit thoroughly. The description reinforces cursor usage but adds no new parameter semantics beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description opens with 'List one page of inboxes that organize conversations in this workspace' – a specific verb, resource, and scope. It clearly distinguishes this paginated list tool from singular siblings like get_inbox.

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 explicitly instructs using after/before cursors to continue pagination and warns that each call returns only one page. It doesn't name alternative tools like get_inbox, but the usage context is clear enough for a list endpoint.

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