Skip to main content
Glama

Press5 launch pad

Get a starter template

get_template
Read-only

All files of one starter template (HTML and CSS as text), with "fields" filled in if given. Change them as the person wants, then publish them with deploy_site { files }. No account needed.

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

Input Schema

NameRequiredDescriptionDefault
fieldsNo
templateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Beyond readOnlyHint=true, it discloses the return format (HTML and CSS as text), that "fields" are substituted into the template, and that no account is required. It does not say what happens when a field key has no matching placeholder or whether the result is a snapshot versus a live reference.

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?

Four short sentences, front-loaded with what is returned, then the workflow, then the auth note. Slight informality ("Change them as the person wants") costs a bit of density but nothing is genuinely wasted.

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?

There is no output schema, and the description compensates by describing the returned file set and its text format, plus the deploy_site handoff. The main residual gap is the `template` identifier format, which an agent needs before it can make the call.

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?

With 0% schema description coverage, the description must carry the burden. It clarifies the `fields` parameter as placeholder substitution values, but gives no meaning for `template` (ID vs. name, presumably from list_templates) or whether fields keys must match placeholders.

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?

"All files of one starter template (HTML and CSS as text)" names the resource, the scope (one template) and the return content, which an agent can distinguish from list_templates without opening a schema. It never explicitly contrasts with that sibling, so it stops short of a 5.

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 the follow-on workflow clearly: edit the returned files, then "publish them with deploy_site { files }", naming the sibling to call next. "No account needed" removes a common precondition guess, but there is no explicit when-not-to-use or guidance on choosing a template value.

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.

Resources