Skip to main content
Glama
Sign In
ClawGrab MCP Server

ClawGrab MCP Server

Official
by getclawgrab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

translate_transcript

Translate transcript text into a chosen target language to localize media content and help users understand it across languages.

Instructions

Translate transcript text into another language.

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>",
      "target_language": "<target_language>"
    },
    "name": "translate_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe text to translate
target_languageYesTarget language (e.g. 'Spanish', 'French', 'Japanese')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It identifies the translation action but says nothing about source-language handling, formatting preservation, limits, permissions, or what the response contains.

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?

The description is a single front-loaded sentence with no wasted wording. It is concise and directly states the action.

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?

For a simple two-parameter translation tool with fully documented schema fields, the description is minimally adequate. However, with no annotations or output schema, it should say more about output, source language behavior, or constraints to be fully complete.

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 100%, so both parameters are already documented. The description adds no meaning beyond the schema, which makes the baseline score of 3 appropriate.

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: translate transcript text into another language. The purpose is clear and distinguishable from read/summarize/extract siblings, but it does not explicitly differentiate itself from alternatives.

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?

No when-to-use guidance, exclusions, prerequisites, or alternative tools are mentioned. The description only implies that it is for translation requests, leaving the agent to infer usage boundaries.

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