Skip to main content
Glama

search

Find matching transcript segments by keyword and return each hit, helping you locate specific spoken content in recorded audio.

Instructions

按关键词搜录音文字,返回命中的段。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keyword": "<keyword>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
keywordYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 burden. It discloses only that matched segments are returned; it says nothing about match semantics (fuzzy vs exact, case, language), result ordering, pagination, or what happens when nothing matches.

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

Conciseness3/5

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

A single short sentence with no wasted wording and the purpose front-loaded, but its brevity reflects under-specification rather than disciplined conciseness.

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?

The tool is simple (2 params, flat schema) and an output schema exists, so the return-format burden is partly lifted. Still, with 0% parameter coverage and no usage routing, an agent cannot tell how limit behaves or when this beats the sibling retrieval tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 only echoes that keyword drives the search. The limit parameter (default 50) is never mentioned, and no matching syntax or max value is given for keyword.

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?

"按关键词搜录音文字,返回命中的段" names a specific verb (搜) plus the resource (录音文字) and the return shape (命中的段). It is clearly distinguishable from get_transcript and list_segments, though it never explicitly states the boundary with those siblings.

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 and no when-not-to-use guidance. Nothing tells the agent when to pick keyword search over list_segments or get_transcript, so the choice must be inferred from the one-word name.

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