Skip to main content
Glama

Deploy a Varity Template

varity_deploy_template

Deploy a public certified Varity template that needs no environment variables; private or secret-bearing templates are rejected, so check template info first.

Instructions

Deploy a public certified Varity template that declares no required environment variables. Private or secret-bearing templates are refused; call varity_template_info first.

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": "varity_deploy_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoMemorable deployment name. Defaults to <template>-derived name if omitted.
templateYesTemplate ID from varity_list_templates.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare this as a non-read-only, non-destructive, open-world, non-idempotent operation, so the safety profile is structured. The description adds real behavioral context annotations cannot: refusal of private/secret-bearing templates and the mandatory pre-check via varity_template_info. It does not cover what is produced on success or how to observe or roll back the deployment, which keeps it from a 5.

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?

Two sentences, with the capability and its hard constraint front-loaded and the prerequisite second. No filler or restatement of the tool name.

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?

For a deploy action with no output schema and non-idempotent, open-world annotations, the description should indicate what the caller gets back or how to follow up, such as a deployment identifier or status check. It covers eligibility and prerequisites well but leaves the post-deploy path unaddressed.

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% and both parameters carry their own descriptions, including the required template ID source (varity_list_templates) and the defaulting behavior of name. The description adds no parameter meaning beyond the schema, so the schema does the work; the baseline for full coverage applies.

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 (deploy) and resource (public certified Varity template) and narrows scope with an explicit constraint: templates must declare no required environment variables. This is materially narrower than a generic deploy tool, so an agent can distinguish it from varity_deploy without opening either schema.

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 states an exclusion (private or secret-bearing templates are refused) and a required prerequisite step (call varity_template_info first), which is clear when-to-use guidance. It stops short of naming the fallback path for secret-bearing templates, e.g. set env variables then use varity_deploy, so the alternative routing is left implicit.

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