Skip to main content
Glama
Sign In
@callirra/mcp

@callirra/mcp

Official
by callirra-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_chat_sessions

Read-onlyIdempotent

Retrieve chat session IDs, titles, and the next pagination cursor to browse and page through existing sessions.

Instructions

List existing chat session IDs, titles and the next pagination cursor.

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

Input Schema

NameRequiredDescriptionDefault
takeNo
cursorNoOffset cursor returned by a prior list call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds the useful fact that a next-page cursor is returned, but says nothing about ordering, default page size, or behavior when the collection is empty.

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 no filler, and the returned-fields information is packed into the same clause rather than a separate boilerplate sentence.

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?

With no output schema, the description usefully names the return shape (IDs, titles, next cursor). However, for a paginated list tool it omits page-size defaults and result ordering, which an agent needs to page correctly.

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?

Schema coverage is 50%: 'cursor' is documented in the schema itself, while 'take' has no description and no default noted anywhere. The description's mention of pagination only restates the cursor parameter and does not compensate for the undocumented page-size parameter or its 1-100 bounds.

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?

States a specific verb (list) and resource (chat sessions) and even enumerates the returned fields, so the agent knows it is a read-only enumeration tool. It does not explicitly contrast itself with get_chat_session or list_chat_messages, so an agent must infer that this is the collection-level listing.

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 verb 'list' — the agent can guess this enumerates sessions before calling get_chat_session. There is no explicit guidance on when to prefer this over get_chat_context, nor any note on how to continue paging beyond the cursor mention.

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