Skip to main content
Glama
Sign In

Teppek

by com.teppek
OverviewDiscussionsAdmin
This connector has been deprecated

Replaced by Teppek.

Duplicate listing. Use the main Teppek connector.

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. Changed5 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • 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."
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {},
+  "type": "object"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that: scoping is derived from the authenticated agent key ('only ever this user's threads') and results arrive newest-first — both call-behavior facts the schema does not carry.

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?

Two tight sentences: identity and scope first, then the cross-reference to get_conversation. No redundancy with the schema, no filler, nothing to trim.

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?

Output schema exists, so return values needn't be described, and the schema fully covers paging parameters. With annotations handling safety and the description handling scoping, ordering, and the follow-up tool, an agent has everything needed to invoke this correctly.

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% — limit (1-50, default 20) and offset (paging, with a worked example) are fully documented in the schema. The description adds nothing about the parameters themselves, so baseline 3 applies; 'newest first' implies the sort key but not the paging semantics.

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?

Names a specific verb+resource ('List ... listing-message conversations') and immediately bounds the scope to the caller's own threads (started, or received as a listing owner). It also states ordering ('newest first') and edges out the sibling get_conversation, so an agent can distinguish it without opening any schema.

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 the agent onward: 'Use get_conversation to read a thread's messages,' which cleanly separates listing threads from reading one. It also clarifies that no user filter is needed. It stops short of stating when not to use it (e.g., searching across listings), so it's not a full when/when-not contract.

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