Skip to main content
Glama
Sign In

RubiConnect

by com.rubiconnect.console
OverviewDiscussionsAdmin

manage_templates

Organizes message templates and manages template folders for an agent profile: batch-moves one or multiple existing templates into a folder (auto-creating the folder if needed) or back to root, creates/renames/deletes/merges template folders, renames templates, or deletes templates. Destructive actions (delete_folder, delete_template) require confirm=true after explicit user confirmation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "manage_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNoOperation to perform: 'move_templates' (default — moves one or more templates into folderName/folderId or back to root), 'create_folder', 'rename_folder', 'delete_folder', 'merge_duplicate_folders' (consolidates duplicate same-name folders into one folder), 'rename_template', or 'delete_template'.move_templates
agentIdNoAgent ID or display name. Uses active agent from context if omitted.
confirmNoMust be set to true after explicit user confirmation for destructive operations (delete_folder, delete_template).
newNameNoNew name when renaming a template (rename_template) or folder (rename_folder).
folderNameNoTarget template folder name for move_templates (auto-created if needed), new folder name for create_folder, or updated name for rename_folder.
moveToRootNoWhen true on move_templates, moves the specified template(s) out of any folder back to root (folderId = null).
folderIdentifierNoExisting template folder ID or name (used for rename_folder or delete_folder, or as target folder for move_templates).
templateIdentifierNoSingle template name or ID (for move_templates, rename_template, or delete_template).
templateIdentifiersNoArray of template names or IDs to batch-move or delete in a single call.
deleteTemplatesInFolderNoFor delete_folder: when false (default), templates inside the deleted folder are safely moved back to root; when true, templates inside the folder are also deleted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"Operation to perform: 'move_templates' (default — moves one or more templates into folderName/folderId or back to root), 'create_folder', 'rename_folder', 'delete_folder', 'rename_template', or 'delete_template'."New value: +"Operation to perform: 'move_templates' (default — moves one or more templates into folderName/folderId or back to root), 'create_folder', 'rename_folder', 'delete_folder', 'merge_duplicate_folders' (consolidates duplicate same-name folders into one folder), 'rename_template', or 'delete_template'."
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "move_templates",
-  "create_folder",
-  "rename_folder",
-  "delete_folder",
-  "rename_template",
-  "delete_template"
-]New value: +[
+  "move_templates",
+  "create_folder",
+  "rename_folder",
+  "delete_folder",
+  "merge_duplicate_folders",
+  "rename_template",
+  "delete_template"
+]
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses that destructive actions require confirm=true after explicit user confirmation and that folders are auto-created, but most of this repeats schema descriptions and it omits permissions, reversibility, and return behavior for mutations.

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?

The description is front-loaded and appropriately sized for a seven-action tool. The long first sentence is dense but earns its place by enumerating the supported operations, and the second sentence highlights the key safety constraint.

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

Completeness4/5

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

For a 10-parameter, multi-action mutation tool with no annotations and no output schema, the description covers all actions and the critical destructive-confirmation requirement. It lacks return-value and permission details, but the schema fully covers parameter semantics, making this adequate for correct invocation.

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 the schema already documents all ten parameters thoroughly. The description adds action grouping context but does not meaningfully extend parameter semantics beyond what the schema provides.

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?

The description states a clear verb and resource: it organizes message templates and manages template folders, then enumerates the exact operations. It implicitly distinguishes itself from create_template by focusing on existing templates, but it does not explicitly name sibling tools or clarify the boundary with list_templates/get_template_detail.

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

Usage Guidelines3/5

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

The action enumeration implies when each operation applies, but there is no explicit guidance on choosing this tool over create_template, list_templates, or get_template_detail. The destructive-action confirmation note is useful but is about safety rather than tool selection.

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

All RubiConnect 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