Skip to main content
Glama
Sign In
Lizard MCP

Lizard MCP

Official
by lizard-build
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List templates

template_list
Read-onlyIdempotent

Find published app templates to deploy, or set mine to list your own and private templates. Inspect required variables with template_show before deployment.

Instructions

Find published app templates to deploy. Set mine to list your own templates, including private ones. Use template_show to inspect required variables before deploying.

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

Input Schema

NameRequiredDescriptionDefault
mineNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds meaningful context the annotations don't: the default visibility filter (published only) versus the private-inclusive scope when mine is set. It doesn't describe pagination or return shape, but for a simple list tool that's a minor 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?

Three short sentences, front-loaded with the primary purpose, then the parameter behavior, then the follow-up tool. Zero filler.

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-only list tool with rich annotations and no output schema, the description covers purpose, filtering behavior, and the natural next step. Return value details are not needed absent an output schema, though a hint that results are what you feed into template_deploy would tighten it.

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 0%, so the description carries the burden for the single `mine` parameter, and it does explain what setting it does ('list your own templates, including private ones'). That is genuine semantic value beyond the bare boolean schema; only the exact default value (false) is left implicit.

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 ('Find published app templates') and clarifies the scope is deployable published templates, which distinguishes it from template_show and template_deploy in the sibling list. An agent can immediately tell this is the discovery step of the template workflow.

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?

Explicitly states the default behavior (published templates), the condition for the alternative ('Set mine to list your own templates, including private ones'), and routes to template_show before deploying. Both when-to-use and a named next-step alternative are present.

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