Skip to main content
Glama
Sign In

Caybl

by ai.caybl
OverviewDiscussionsAdmin

Import a Template Gallery template into the Caybl workspace

gtm_import_template

Import a template found with gtm_template_lookup into the container's Caybl workspace (a draft, never live). Only templates that appear in the live gallery can be imported. Dry run by default. After applying, the result lists the template's settings and the sandbox permissions it asks for; show those to the user. Then create a tag with gtm_upsert_tag kind=template.

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": {
      "template": "<template>"
    },
    "name": "gtm_import_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
templateYesThe template `id` from gtm_template_lookup (or owner/repository as shown there).
containerNoContainer public id like 'GTM-ABC123', from gtm_list_containers.
workspaceNoName of an existing workspace to draft into instead of "Caybl changes" (created automatically).
validateOnlyNoDefault TRUE: a dry run that shows exactly what would change and changes nothing. Show the user the result, and only call again with validateOnly=false once they've agreed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false and openWorldHint=true; the description adds substantive behavior beyond that: the import lands in a draft and is 'never live', it is a dry run by default, and the result enumerates settings plus requested sandbox permissions. It also instructs the agent to surface those permissions to the user, which is exactly the safety context a mutation tool needs.

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?

Front-loaded with the action and scope, then the constraint, then the default mode, then the post-apply workflow. Every sentence carries information, though the closing gtm_upsert_tag instruction is a slight drift into orchestration rather than tool definition.

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

Completeness5/5

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

No output schema exists, and the description compensates by describing what the result contains (settings and requested sandbox permissions) and what to do with it. For a four-parameter mutation tool with a dry-run default, nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds workflow meaning the schema does not: validateOnly is framed as a two-call confirmation loop ('only call again with validateOnly=false once they've agreed') and workspace is framed as an alternative to the auto-created 'Caybl changes' draft. It stops short of adding format detail for template/container, which the schema already covers.

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 ('Import a template ... into the container's Caybl workspace') and immediately scopes it against the sibling that finds templates ('found with gtm_template_lookup'). An agent can distinguish it from gtm_template_lookup and gtm_upsert_tag without opening any schema.

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 explicit preconditions ('Only templates that appear in the live gallery can be imported'), states the default mode ('Dry run by default'), and prescribes the follow-up step ('Then create a tag with gtm_upsert_tag kind=template'). The when-to-use and what-to-do-next path is fully spelled out.

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

All Caybl toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources