Skip to main content
Glama

Teppek

by com.teppek.mcp
OverviewDiscussionsAdmin

list_conversations

Read-only

List the user's OWN listing-message conversations (threads they started, or received as a listing owner), newest first. Resolved from the authenticated agent key — only ever this user's threads. Use get_conversation to read a thread's messages.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results to return per page, 1-50. Default 20. Example: 10.
offsetNoHow many results to skip, for paging. Default 0. Example: 20 returns the second page when limit is 20.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum results to return per page, 1-50. Default 20. Example: 10."
    • addedInput schema / properties / offset / description
      Added value: +"How many results to skip, for paging. Default 0. Example: 20 returns the second page when limit is 20."
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {},
+  "type": "object"
+}
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Adds value beyond annotations (readOnlyHint/openWorldHint already cover the safety profile) by disclosing sort order ('newest first') and the auth-derived scoping ('resolved from the authenticated agent key — only ever this user's threads'). It doesn't mention pagination behavior, but the schema's limit/offset already covers that.

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 sentences, all load-bearing: scope, ordering/identity constraint, and next-step pointer. The key constraint (own threads only) is front-loaded.

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?

With an output schema present and both params fully documented, the description only needs to establish scope, ordering, and the sibling relationship — all of which it does. A note on pagination expectations would round it out, but nothing essential is missing.

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 both limit and offset are fully documented with defaults, bounds, and examples. The description adds no parameter meaning beyond that, so baseline 3 applies.

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?

States a specific verb and resource ('List ... listing-message conversations') with precise scope: threads the user started or received as listing owner. The parenthetical definition distinguishes list_conversations from sibling listings/message tools at a glance.

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?

Explicitly routes to get_conversation for reading a thread's messages, which is the natural next step and removes ambiguity about what this tool returns. No explicit when-not conditions (e.g., vs. semantic_search or search_listings), but the usage context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Teppek toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources