Skip to main content
Glama

list_segments

Lists recording segments within an optional start/end time range, enabling you to filter recordings by date or date-time and locate relevant transcript sections.

Instructions

按时间段列出录音段。start/end 用 2026-11-13 或 2026-11-13 14:30,可只给一个或都不给。

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

Input Schema

NameRequiredDescriptionDefault
endNo
limitNo
startNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. '列出' (list) implies a read that returns rather than mutates, and the note that range bounds can be omitted implies an unbounded listing is legal — both useful. It says nothing about ordering, truncation, or the default limit of 100, which are the behaviors an agent most needs to know here.

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 compact sentences: the action and scope come first, then the parameter format note. Every clause carries information and there is no filler.

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?

An output schema exists, so return values need not be described. But for a three-parameter tool with zero schema coverage and no annotations, the missing discussion of limit/default 100 and what happens when results exceed it leaves a real gap for correct invocation.

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 0%, so the description must compensate, and it does so for two of three parameters by giving concrete accepted formats ('2026-11-13' or '2026-11-13 14:30') and stating they are optional. The third parameter, limit, is never mentioned, leaving the caller to discover the default and its effect on results.

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?

The description names a specific verb and resource ('按时间段列出录音段' — list recording segments by time period) plus the scoping mechanism. It is clear what the tool returns at a coarse level, though it never distinguishes itself from siblings like get_transcript or search, which an agent might plausibly reach for instead.

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?

It tells the agent that start and end are flexible ('可只给一个或都不给'), which is useful usage context for optional scoping. However, it offers no when-to-use versus alternatives guidance — nothing says whether this is the right tool for a full listing versus get_transcript or search.

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