Skip to main content
Glama

List Hostilo site templates

list_templates
Read-onlyIdempotent

Lists ready-made Hostilo site designs (café menu, local service business with industries, and more): slug, name, description, variants and the fields you can fill in (name, phone, address, colour…), plus a live preview URL. Use create_site with template, template_variant, template_fields and lang to create a site from one.

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
langNoLanguage of names and descriptions (default en).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is lower. The description earns credit by disclosing what the response contains, including variant information and a live preview URL, which the annotations do not convey and no output schema exists to cover.

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?

Two sentences, front-loaded with the core action and return contents, followed by the handoff to create_site. The parenthetical examples ("café menu, local service business with industries, and more") are mildly verbose but do real work in conveying template variety.

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 simple, single-optional-parameter read tool with full annotation coverage, the description covers purpose, returned fields, and next step. Missing only minor operational detail such as whether the list is static or how many templates are returned, which is acceptable given the tool's low complexity.

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 coverage is 100% and the single lang parameter is documented in the schema with its enum and default, so the baseline is 3. The description mentions lang only as an argument to create_site and does not add that this tool localizes names and descriptions, so it adds no meaning beyond the schema.

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 (lists ready-made Hostilo site designs) and enumerates the returned fields: slug, name, description, variants, fillable fields, and a live preview URL. That detail distinguishes it cleanly from siblings like list_sites, which lists created sites rather than templates.

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?

Explicitly names the follow-up action and the exact parameters to use: create_site with template, template_variant, template_fields and lang. There is no explicit exclusion or when-not-to-use guidance (e.g., versus list_sites), which keeps it short of a 5.

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.