Skip to main content
Glama
Sign In
Meet Rupert MCP Server

Meet Rupert MCP Server

by Meet-Rupert
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_chat_threads

List recent conversation threads with titles and thread IDs, sorted newest first, enabling you to resume any thread using ask_in_thread.

Instructions

List your recent Meet Rupert conversation threads with their titles and threadIds, so you can resume one with ask_in_thread. Returns the most recent threads first.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden of behavioral disclosure. It specifies that threads are 'recent' and owned by the user ('your'), includes return content (titles, threadIds), and notes ordering ('Returns the most recent threads first'). It does not mention pagination or limits, but for a simple read-only list, this is reasonably transparent.

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 description is extremely concise: two short sentences that front-load the core purpose and then add the ordering detail. Every word earns its place, with no redundant phrasing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (zero parameters, no output schema), the description is complete. It fully explains what the tool returns, for whom, and in what order, with no confusing gaps. A simple list tool needs no further elaboration.

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?

The tool has zero parameters, so according to the rubric baseline is 4. The description cannot add parameter-level detail, but it documents the output semantics (titles, threadIds, ordering) that would otherwise be expected from parameters.

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?

The description uses a specific verb+resource ('List your recent Meet Rupert conversation threads') and clearly states what is returned (titles and threadIds). It distinguishes itself from siblings like create_chat_thread and ask_in_thread by explicitly mentioning resuming with ask_in_thread.

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 provides clear usage context by stating 'so you can resume one with ask_in_thread', directly linking this tool to its intended follow-up. However, it does not explicitly mention when not to use it (e.g., for creating new threads) or name alternative tools beyond the implicit reference.

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