Skip to main content
Glama
Sign In

QuintaDB

by ua.com.quintadb
OverviewDiscussionsAdmin

update_record_template

Idempotent

Update an existing PDF/HTML record template (its name and/or body). Use this, not create_record_template, when the user asks to 'change'/'update' an existing print template — it keeps the template's ties to print buttons and the payment flow.

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": {
      "app_id": "<app_id>",
      "template_id": "<template_id>"
    },
    "name": "update_record_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoNew HTML body of the template (optional; the fields' html_name without brackets)
nameNoNew template name (optional)
app_idYesProject ID (from list_projects)
template_idYesID of the record template to update

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / body / description
      Previous value: -"Нове HTML тіло шаблону (опційно, html_name полів без дужок)"New value: +"New HTML body of the template (optional; the fields' html_name without brackets)"
    • changedInput schema / properties / name / description
      Previous value: -"Нова назва шаблону (опційно)"New value: +"New template name (optional)"
    • changedInput schema / properties / template_id / description
      Previous value: -"ID шаблону запису (record template), який треба оновити"New value: +"ID of the record template to update"
  2. Added

TDQS

A4.3/5.0
Behavior3/5

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

The description mentions that using this tool 'keeps the template's ties to print buttons and the payment flow,' which adds valuable behavioral context regarding the operational side of the system. However, it doesn't disclose technical behavioral traits like mutation limits, atomicity, or rate limits, relying instead on the provided annotations (e.g., `idempotentHint: true`).

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?

The definition is concise and highly effective. The first sentence defines the core action, while the second sentence immediately provides the critical distinction and usage context, both of which are essential for an AI agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of templates (which often involve dependencies), the description clearly addresses the key behavioral difference from the create sibling. Combined with the 100% schema coverage and `idempotentHint`, the description provides all necessary context for an agent to select and invoke the tool confidently.

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?

The schema coverage is 100% for a 4-parameter tool, making the baseline for semantic clarity a 3. The description specifies which fields ('name' and 'body') can be modified, which reinforces the parameter descriptions in the schema. It adds value without going beyond what is already structured.

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 purpose is very clear: to update an existing PDF/HTML record template. It specifies which resources (name and body) can be changed. Crucially, it distinguishes this from `create_record_template` based on whether the action is 'change' or 'update' an existing template.

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?

The description provides an explicit usage guideline by contrasting it with the sibling tool `create_record_template`. It defines the context ('change'/'update' an existing print template) and explains the benefit of using this specific tool (keeps ties to print buttons and payment flow). This eliminates ambiguity.

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

All QuintaDB toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources