Skip to main content
Glama

TranscriptLab

Begin audio upload

transcriptlab_begin_audio_upload

Create a signed direct-upload session for an opened audio file. App-facing only: the uploader view calls it, not the model.

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": {
      "name": "<name>",
      "bytes": "<bytes>",
      "content_type": "<content_type>"
    },
    "name": "transcriptlab_begin_audio_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
bytesYes
content_typeYesMedia MIME type.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-destructive, closed-world operation, so the safety profile is covered. The description adds that a signed upload session is created rather than an actual byte transfer, but it says nothing about session lifetime, required authorization, or what the caller must do with the signed target.

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?

Two short sentences with no filler; the action statement comes first and the caller restriction second, so the most important routing information is front-loaded.

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?

There is no output schema, yet the tool's whole purpose is to return a signed upload target the caller must use — that return contract is unstated. Combined with undocumented parameters and no session-expiry or size-limit context, the definition is thin for a session-creating mutation.

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 only 33% (only content_type carries a description and pattern). The description does not explain name, bytes, or the 2 GB ceiling that constrains the upload, leaving two of three parameters with no meaning added anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Create a signed direct-upload session for an opened audio file.' It also distinguishes its role from the rest of the toolset by noting it is app-facing and not intended for model invocation, which no sibling name alone would convey.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit exclusion: 'App-facing only: the uploader view calls it, not the model.' That is a clear when-not-to-use statement an agent can act on directly, which is stronger than typical guidance found in comparable definitions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.