Skip to main content
Glama
Sign In
Tailprint

Tailprint

by coheroseb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_templates

Retrieve available Tailwind CSS document templates—including invoices, certificates, reports, resumes, labels, receipts, quotes, and contracts—to select one for PDF generation.

Instructions

Returns the catalog of available pre-designed Tailwind CSS document templates (Invoices, EU Factur-X, Certificates, Executive Reports, Resumes, Shipping Labels, Event Passes, POS Receipts, Quotes, NDAs, Statements, Presentations, Contracts).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.0

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 must carry the behavioral burden. It does convey that the tool returns a static catalog of available templates (a safe read), but says nothing about the format or shape of returned entries, whether the catalog is stable, or what identifiers an agent needs to pass to sibling tools.

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?

A single front-loaded sentence states the return value first and then qualifies it. The long parenthetical enumeration of template types is informative for a discovery tool, though thirteen items is at the edge of what is worth including.

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 zero-parameter list tool with no output schema, the main missing piece is what the returned items look like — the agent cannot tell whether it receives names, IDs, or full objects, which matters because those values must feed get_template_source.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond what the empty schema already states. Baseline 4 applies.

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 uses a specific verb ('Returns the catalog') plus a precise resource ('pre-designed Tailwind CSS document templates') and enumerates the template categories, so the agent knows exactly what this lists and can tell it apart from get_template_source or render_template. It stops short of explicitly naming the sibling it is not.

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?

Usage is only implied: an agent can infer this is the discovery/listing step before fetching a template's source, but the description never says when to call it versus get_template_source, nor does it mention any prerequisites or exclusions.

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