Skip to main content
Glama
Sign In
ClawGrab MCP Server

ClawGrab MCP Server

Official
by getclawgrab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

extract_quotes

Extract memorable, shareable quotes from a transcript so you can highlight key lines for social posts, summaries, or presentations.

Instructions

Extract the most memorable and shareable quotes from a transcript.

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": {
      "text": "<text>"
    },
    "name": "extract_quotes"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe transcript text to extract quotes from

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/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 disclosure burden and falls well short. It does not say how many quotes are returned, whether they are verbatim excerpts or paraphrased, whether output is a list or string, or that the input must meet the 50-character minimum enforced by the schema.

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 front-loaded sentence with no filler or redundancy. It is efficient, but its brevity is close to under-specification given the tool has no annotations to fall back on.

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 — one required string parameter, no nested objects, no output schema — so a short description is defensible. Still, nothing is said about the shape or volume of the returned quotes, which is the main thing an agent would need in order to use the result 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?

There is a single parameter and schema coverage is 100%, so the schema already documents 'text' fully, including the minLength constraint. The description only echoes this by saying quotes come 'from a transcript', adding no format, size, or content expectations beyond the schema.

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?

States a specific verb and resource: 'Extract' plus 'quotes', qualified by 'most memorable and shareable' and scoped by 'from a transcript'. An agent can tell this is a selection/extraction tool rather than a generation or summarization tool, though it never names a sibling to contrast against.

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?

Usage is only implied: the phrase 'from a transcript' signals the required input, and 'memorable and shareable' hints at the selection criterion. There is no explicit when-to-use versus summarize_text or get_transcript, and no stated exclusions or prerequisites.

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