Skip to main content
Glama

templates

Destructive

Save the current project as a reusable starting point, list saved starting points, open one to replace the current project with undo support, or delete after confirmation.

Instructions

The person's templates (saved whole projects to start from), like Dinoctor's Templates page. action list (read-only), save (name: saves the project as it is now), open (id: replaces the open project with the template; one undo step brings it back), delete (id: for good, needs confirm: true after the person agrees). For .dino project files use open_project / save_project; for shot recipes use samples.

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": {
      "action": "<action>"
    },
    "name": "templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoA template id from list (open, delete).
nameNoFor save: the template's name.
actionYesWhat to do (see the description).
confirmNoFor delete: true only after the person agreed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.2
    • addedInput schema / properties / action / description
      Added value: +"What to do (see the description)."
    • addedInput schema / properties / confirm / description
      Added value: +"For delete: true only after the person agreed."
    • addedInput schema / properties / id / description
      Added value: +"A template id from list (open, delete)."
    • addedInput schema / properties / name / description
      Added value: +"For save: the template's name."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare destructiveHint=true but say nothing about recovery or consent; the description supplies both — 'open... one undo step brings it back' and 'delete... for good, needs confirm: true after the person agrees'. It also flags list as read-only, giving a per-action safety profile beyond the tool-level flags.

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?

Front-loaded with the resource definition, then a compact per-action list with effect in parentheses, then a single routing sentence. Dense but efficient; the parenthetical glosses (e.g., 'name: saves the project as it is now') partially restate schema fields, which is the only mild redundancy.

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?

With no output schema, the description still conveys the shape of list results indirectly ('id from list') and fully covers mutation effects, consent requirement, and undo behavior. The only gap is that it doesn't state what list returns or ordering, which is minor for a straightforward CRUD-style tool.

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 100%, so the baseline is 3, but the description adds cross-parameter meaning the schema lacks: which action each parameter belongs to (id for open/delete, name only for save) and that id comes from a prior list call. That is a modest genuine addition over the per-field schema text.

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?

The description opens with a concrete noun phrase ('The person's templates (saved whole projects to start from)') and then enumerates all four actions with their effects, so an agent knows exactly what the resource is and what each action does. It also names the siblings it is not (open_project/save_project, samples), making it distinguishable without opening a schema.

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?

Routing is explicit: project files go to open_project/save_project, shot recipes go to samples. Within the tool, each action carries its own condition (save captures current state, open replaces the working project, delete requires confirm: true after the person agrees), which covers both when-to-use and the guarded case.

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