Skip to main content
Glama
Sign In
Lizard MCP

Lizard MCP

Official
by lizard-build
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Show template

template_show
Read-onlyIdempotent

Read a template's services, addons and required variables before deployment. Pass the ID or slug returned by template_list to verify configuration and avoid setup errors.

Instructions

Read a template's services, addons and required variables before deployment. Pass the ID or slug returned by template_list.

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

Input Schema

NameRequiredDescriptionDefault
templateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is covered; the description adds the return payload (services, addons, required variables), which matters because there is no output schema. It does not cover what happens on an unknown ID or whether the read is scoped to a workspace, but that is a minor residual gap.

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, zero filler, with the purpose and the parameter-sourcing instruction both front-loaded. Nothing is repeated from the title 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 one-parameter read tool with no output schema, the description supplies both the input source convention and the shape of the returned data. Missing only error/not-found behavior and whether output is workspace-scoped, which are minor for this tool class.

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?

With 0% schema description coverage, the single parameter is completely undocumented structurally. The description compensates by stating the accepted value types (ID or slug) and where to obtain them (template_list), which is exactly the missing information an agent needs to fill the field.

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 (Read) and resource (template) and enumerates what is returned: services, addons, required variables. The phrase 'before deployment' distinguishes it from template_deploy, and naming template_list as the source of IDs separates it from the list tool.

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?

'Read ... before deployment' gives a clear usage context, and the instruction to pass an ID or slug from template_list establishes the prerequisite chain. It stops short of explicit exclusions or a direct 'use template_deploy to actually deploy' contrast, but the implied workflow is easy to infer.

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

Deploy Server

Other Tools