Skip to main content
Glama
Sign In
ClawGrab MCP Server

ClawGrab MCP Server

Official
by getclawgrab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

summarize_text

Converts transcript text into a short AI-generated bullet-point summary, helping users quickly grasp key points from long media transcripts.

Instructions

Generate a short AI bullet-point summary from transcript text.

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": "summarize_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe transcript text to summarize

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that output is AI-generated, short, and bullet-pointed, which is useful behavioral context, but says nothing about length limits, handling of long transcripts, cost/latency, or failure modes such as non-transcript input.

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?

One front-loaded sentence with no filler; the output format is stated before the input. It is efficient, though so terse that there is little structure beyond the single clause.

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

Completeness4/5

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

For a simple one-parameter generation tool with a fully documented schema and no output schema, the description covers input source and output shape adequately. Gaps around length and large-input behavior are minor given the tool's simplicity.

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?

With a single parameter and 100% schema description coverage, the schema already documents "text" as the transcript to summarize. The description's phrase "from transcript text" merely restates that, adding no format, size, or truncation guidance.

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 ("Generate") and resource ("summary") plus the output shape ("short AI bullet-point summary") and input source ("transcript text"). That distinguishes it implicitly from siblings like generate_blog_post or extract_quotes, though it never names an alternative explicitly.

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 mention of alternatives such as extract_quotes or generate_social_posts when a different output is wanted. The only implied usage is that the input must be transcript text.

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