Skip to main content
Glama
Sign In
TimWongUp

AgentNave

by TimWongUp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List handles and saved conversations

list
Read-onlyIdempotent

Retrieve invocation metadata and saved conversations newest first, filter by meetings or task conversations, set a recent limit, and open a read-only dashboard.

Instructions

List invocation metadata and saved conversations, newest first; open a read-only dashboard. writable=false: continue at the owning server or when idle. Private: never send to seats.

Input Schema

NameRequiredDescriptionDefault
kindNoOnly meetings or only task conversations.
limitNoMost recent conversations; defaults to 10, at most 200.

Output Schema

NameRequiredDescriptionDefault
totalYes
invocationsYes
unavailableYes
conversationsYes
dashboard_urlNo
dashboard_errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.65.0
    • changedInput schema / properties / limit / default
      Previous value: -20New value: +10
    • changedInput schema / properties / limit / description
      Previous value: -"Most recent conversations."New value: +"Most recent conversations; defaults to 10, at most 200."
  2. Changed1 schema field changedv0.53.1
    • changedInput schema / properties / kind / description
      Previous value: -"Only shows or only task conversations."New value: +"Only meetings or only task conversations."
  3. Changed1 schema field changedv0.49.0
    • addedInput schema / additionalProperties
      Added value: +false
  4. Changed2 schema fields changedv0.41.0
    • addedOutput schema / $defs / InvocationErrorPayload
      Added value: +{
+  "properties": {
+    "code": {
+      "title": "Code",
+      "type": "string"
+    },
+    "message": {
+      "title": "Message",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "title": "InvocationErrorPayload",
+  "type": "object"
+}
    • addedOutput schema / $defs / InvocationListItem / properties / error
      Added value: +{
+  "$ref": "#/$defs/InvocationErrorPayload"
+}
  5. Addedv0.35.0

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so "writable=false" mostly restates structured data. The description does add two useful behavioral facts: results are ordered newest-first, and the data is private and must not be sent to seats. However, "open a read-only dashboard" is left unexplained, leaving ambiguity about whether a side effect occurs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the listing purpose, but the remaining sentences are cryptic fragments ("continue at the owning server or when idle") that read as leaked internal notes rather than agent-facing guidance. Those lines consume space without conveying actionable meaning.

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

Completeness2/5

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

An output schema exists, so return values need not be explained, but the description still leaves core questions open for a zero-required-parameter listing tool: what "invocation metadata" contains, whether the dashboard clause is an action, and how results differ when kind is set. Given the ambiguity, the description is not sufficient to call the tool confidently.

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 kind (meetings vs task conversations) and limit (1-200, default 10) are fully documented in the schema. The description adds nothing about either parameter, only the ordering. Baseline 3 applies when the schema does all the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

It does state a specific verb and resource ("List invocation metadata and saved conversations, newest first"), which is enough to distinguish it from read_conversation. But the second clause, "open a read-only dashboard," introduces a second, unexplained capability, and the title's "handles" never matches the description's "invocation metadata." The agent cannot tell exactly what one call returns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is fragmentary jargon: "writable=false: continue at the owning server or when idle" and "Private: never send to seats." Neither tells the agent when to pick list over siblings like list_members or read_conversation. No exclusion or alternative routing is given.

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