Skip to main content
Glama

list_says

Returns all spoken feedback fragments with timestamps, providing issue anchors for tracing voice evidence.

Instructions

All spoken feedback fragments with timestamps — the issue anchors

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose that the result is complete ('All') and timestamped, implying no filtering and chronological relevance, but it says nothing about ordering, volume, pagination, or how fragments relate to segments or sessions. Read-only behavior is only inferred from the word 'list'.

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

Conciseness4/5

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

A single compact phrase with zero filler, and the identifying detail (timestamps, issue anchors) is front-loaded. It is arguably too compressed rather than padded, but every word present earns its place.

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?

With no parameters, no annotations, and no output schema, the description is the only source of behavioral information, and it is thin. The term 'issue anchors' is unexplained jargon, and nothing tells the agent how these fragments relate to sibling resources or what a calling agent should expect to do with them.

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 schema has zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. No parameter meaning is lost because none exists.

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?

The description names a specific resource — spoken feedback fragments with timestamps — and adds the interpretive hint 'issue anchors'. But it is a noun phrase rather than a verb+resource statement, and it does nothing to separate this from sibling listing tools such as list_segments or the transcript-oriented get_asr. An agent knows roughly what comes back but not precisely what distinguishes this list.

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?

There is no when-to-use guidance, no prerequisites, and no named alternative. 'Issue anchors' faintly implies a troubleshooting use case, but the agent must guess whether to reach for this versus list_segments or get_asr when investigating spoken feedback.

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