Skip to main content
Glama
Sign In
aspa-mcp

aspa-mcp

by octos-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Listar conversas

aspa_list_conversations
Read-only

List open Aspa Chat (WhatsApp) support conversations with contact, assigned agent, last activity, and unread status, using filters for tab, status, and paging.

Instructions

List open Aspa Chat (WhatsApp) support conversations: index, contact, assigned agent, last activity time and unread flag.

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

Input Schema

NameRequiredDescriptionDefault
tabNoPanel filter tab. Defaults to todos.
limitNoMaximum conversations to return (default 50).
orderNorecentes (default) or antigas (oldest first).
cursorNonext_cursor from the previous page.
filtersNoPanel list filters, applied only for this listing and removed afterwards.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds value beyond that by enumerating the returned fields (index, contact, assigned agent, last activity, unread flag), which matters because no output schema exists. However, it says nothing about pagination behavior, rate limits, or how many pages are typically needed.

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 front-loaded sentence with zero filler. The scope qualifier "open" comes early and the returned fields follow compactly.

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 five-parameter, read-only list tool with no output schema, the description is largely sufficient: it establishes scope and enumerates the returned fields. The remaining gap is the absence of guidance on paging through results or on how the filter tabs differ operationally.

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 every parameter — the tab enum, limit, order, cursor, and the filters array — is already documented in the schema, including defaults and bounds. The description adds no additional meaning about how these parameters interact (for example, whether filters reset with cursor paging).

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 — "List open Aspa Chat (WhatsApp) support conversations" — and names the fields surfaced. The word "open" implicitly separates it from aspa_list_concluded, but no sibling is named explicitly.

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 by the word "open": an agent can infer this is the default inbox listing and not the concluded-archive or message-search tool. There is no explicit when-to-use statement, no mention of when to prefer aspa_search_conversation or aspa_list_concluded, and no prerequisites such as authentication.

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