Skip to content

Robot help: readable parameter types and published Robot names #641

Open

Description

@kvz

Why

getRobotHelp() backs the MCP tool transloadit_get_robot_help, and since transloadit/content#7165 it also backs the WebMCP get_robot_docs tool on the docs pages. Agents read each parameter's type to work out what to send, and some types don't say:

  • In @transloadit/node 6.6.0, /image/resize returns use with type union<union<string | [object Object] | [object Object]> | object>.
  • In 4.14.0, /image/resize width is union<ZodEffects | ZodEffects>.

listRobots() also derives names from schema keys, so the catalog lists /digital/ocean/import and /digital/ocean/store. The published names are /digitalocean/*. isKnownRobot() accepts both spellings, but getRobotHelp() looks up metadata under /digital/ocean/*, so /digitalocean/import and /digitalocean/store come back with the placeholder summary (Robot /digitalocean/store) and no examples.

What

  • Render nested object and effect types readably, for example number | string (expression), instead of [object Object] or ZodEffects.
  • Make listRobots() return the published Robot names, and resolve metadata for them in getRobotHelp().

Found during council review of transloadit/content#7165.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions