Skip to main content
Glama

Get robot parameter help

transloadit_get_robot_help

Get documentation for Transloadit media processing robots, including summaries, parameter details, and usage examples for video encoding, image manipulation, and file conversion tasks.

Instructions

Returns a robot summary and parameter details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
robot_nameNo
robot_namesNo
detail_levelNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
robotNo
robotsNo
statusYes
not_foundNo

Implementation Reference

  • The handler for the 'transloadit_get_robot_help' tool. It processes the input (robot_name/robot_names), fetches robot information using 'getRobotHelp', and formats the response.
    ({ robot_name, robot_names }) => {
      const splitComma = (value: string): string[] =>
        value
          .split(',')
          .map((part) => part.trim())
          .filter(Boolean)
    
      const prefersSingle =
        typeof robot_name === 'string' && robot_name.trim() !== '' && !robot_name.includes(',')
    
      const requested =
        robot_names && robot_names.length > 0
          ? robot_names
          : robot_name
            ? splitComma(robot_name)
            : []
    
      if (requested.length === 0) {
        return buildToolError('mcp_missing_args', 'Provide robot_name or robot_names.')
      }
    
      const robots: Array<{
        name: string
        summary: string
        required_params: unknown[]
        optional_params: unknown[]
        examples?: unknown[]
      }> = []
      const notFound: string[] = []
    
      for (const name of requested) {
        if (!isKnownRobot(name)) {
          notFound.push(name)
          continue
        }
        const help = getRobotHelp({
          robotName: name,
          detailLevel: 'full',
        })
    
        robots.push({
          name: help.name,
          summary: help.summary,
          required_params: help.requiredParams,
          optional_params: help.optionalParams,
          examples: help.examples,
        })
      }
    
      if (prefersSingle) {
        return buildToolResponse({
          status: 'ok',
          robot: robots[0],
          not_found: notFound.length > 0 ? notFound : undefined,
        })
      }
    
      return buildToolResponse({
        status: 'ok',
        robots,
        not_found: notFound.length > 0 ? notFound : undefined,
      })
  • Registration of the 'transloadit_get_robot_help' tool within the server.
    server.registerTool(
      'transloadit_get_robot_help',
      {
        title: 'Get robot parameter help',
        description: 'Returns a robot summary and parameter details.',
        inputSchema: getRobotHelpInputSchema,
        outputSchema: getRobotHelpOutputSchema,
      },
  • Schema definition for the 'transloadit_get_robot_help' tool.
    {
      name: 'transloadit_get_robot_help',
      title: 'Get Robot Help',
      description: 'Returns a robot summary and parameter details.',
      inputSchema: {
        type: 'object',
        additionalProperties: false,
        properties: {
          robot_name: { type: 'string' },
          robot_names: { type: 'array', items: { type: 'string' } },
        },
      },
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 burden of behavioral disclosure. It states the tool returns information, implying it's a read-only operation, but doesn't specify authentication requirements, rate limits, error handling, or output format (though an output schema exists). For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior beyond basic purpose.

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, efficient sentence with zero waste: 'Returns a robot summary and parameter details.' It's front-loaded with the core action and resource, making it easy to parse. Every word contributes to the purpose without redundancy or fluff.

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?

Given the tool's moderate complexity (3 parameters, no annotations, but with an output schema), the description is minimally complete. It states what the tool does but lacks details on usage, parameters, and behavior. The presence of an output schema means the description doesn't need to explain return values, but it should cover more context for effective tool selection and invocation.

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 schema provides no parameter descriptions. The description mentions 'parameter details' but doesn't explain what the parameters (robot_name, robot_names, detail_level) mean or how they interact (e.g., if robot_name and robot_names are mutually exclusive). It adds minimal semantic value beyond the schema's structure, failing to compensate for the low coverage.

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

Purpose3/5

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

The description states the tool 'Returns a robot summary and parameter details,' which provides a clear verb ('Returns') and resource ('robot summary and parameter details'), making the purpose understandable. However, it lacks specificity about what 'robot' refers to in the Transloadit context and doesn't differentiate from sibling tools like 'transloadit_list_robots' (which likely lists robots without details). This results in a vague but adequate purpose statement.

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?

The description offers no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a robot name), exclusions, or how it compares to siblings such as 'transloadit_list_robots' (for listing) or 'transloadit_lint_assembly_instructions' (for validation). Without any usage context, the agent must infer from the name and schema alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/transloadit/node-sdk'

If you have feedback or need assistance with the MCP directory API, please join our Discord server