Skip to main content
Glama

Kite Discord Bot Builder

Add template

install_template

Adds a template to an app: its commands, event listeners, messages and stored variables, with the parameters filled in. Messages the template posts in a channel are posted right away. Templates not made by Kite are made by other users, so tell the user who made it and ask before adding one. Get the template with get_template and app_id first, and ask the user for the parameters you can't pick from list_channels and list_roles. When the app has a command with the same name, the template's command gets a number, like /giveaway-2, so tell the user the names the result has.

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": {
      "app_id": "<app_id>",
      "template_id": "<template_id>"
    },
    "name": "install_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsNoThe keys of the commands and event listeners to add. Defaults to all of them. Messages and stored variables are always added, the others use them.
app_idYesThe ID of the app, from list_apps.
messagesNoFor messages with written_by_user, the message like Discord's API takes it, by the message's key. Without it, it's the template's text.
server_idNoThe ID of the server, from list_servers, the channels of the parameters are in. Needed when a message is posted.
parametersNoValues of the parameters by their key. Channels and roles are their IDs, yes/no ones (type boolean) are true or false.
template_idYesThe ID of the template, from search_templates.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / parameters / description
      Previous value: -"Values of the parameters by their key. Channels and roles are their IDs."New value: +"Values of the parameters by their key. Channels and roles are their IDs, yes/no ones (type boolean) are true or false."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already state this is a non-read-only, non-destructive, non-open-world mutation. The description adds important behavior beyond annotations: messages posted by the template are posted immediately, non-Kite templates require telling the user who made it and asking consent, and command name collisions are renamed like /giveaway-2. It does not cover permissions, failure behavior, or full result shape, but it is strong for an annotated mutation.

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 front-loaded with the purpose, then adds side effects, consent requirements, prerequisites, and collision behavior in a compact sequence. Each sentence carries actionable information, and there is no redundant restatement of schema or annotations.

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 complex template-install mutation with nested objects and no output schema, the description covers purpose, immediate posting side effects, non-Kite consent, prerequisite lookup, and command name collision handling. It is nearly complete, though it does not explain failure modes, permissions, or the full result structure beyond noting that renamed command names should be reported to the user.

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 six parameters in detail, including nested items, messages, and parameters. The description adds workflow context for sourcing parameter values from list_channels and list_roles, but it does not add syntax or semantics for items, messages overrides, or server_id beyond what the schema provides.

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?

The description gives a specific verb and resource: 'Adds a template to an app', and enumerates what gets added (commands, event listeners, messages, stored variables). This clearly distinguishes it from sibling tools like create_command or create_event_listener, which add individual entities rather than installing a template.

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

Usage Guidelines4/5

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

It gives clear prerequisites and parameter-sourcing guidance: get the template with get_template and app_id first, ask the user for parameters not obtainable from list_channels and list_roles, and ask before adding templates not made by Kite. It does not explicitly state when to prefer install_template over manually creating commands/event listeners, so it falls just short of full when/when-not guidance.

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.