Skip to main content
Glama
Sign In
aspa-mcp

aspa-mcp

by octos-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Conversas concluídas

aspa_list_concluded
Read-only

List concluded support conversations from the last week by default, with optional name search and pagination to review resolved chats.

Instructions

List concluded conversations (last week by default), with optional name search and pagination.

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

Input Schema

NameRequiredDescriptionDefault
queryNo
pageNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, open-world operation. The description adds useful context about the default time window and optional search/pagination, but it does not explain return shape, page size, ordering, or any rate limits.

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?

The definition is a single, front-loaded sentence with no wasted wording. It efficiently communicates resource, default behavior, and optional capabilities.

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 read-only list tool with annotations covering safety, the description covers enough to call it at a basic level. It remains incomplete about return values and pagination mechanics, which matters more because there is no output schema.

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 0%, so the description must compensate. It identifies that one parameter supports name search and the other supports pagination, which adds meaning beyond the bare schema, but it does not clarify matching behavior, page size, or what pageNumber controls beyond being pagination.

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 states a specific verb and resource: list concluded conversations. It clearly separates this from active-conversation listing by specifying the concluded status, but it does not explicitly name or contrast with sibling tools such as aspa_list_conversations or aspa_search_conversation.

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 description implies when to use it by specifying 'concluded conversations' and a default last-week window. However, it gives no explicit when-not guidance or alternatives, such as when to use the general conversation list or conversation search instead.

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