Skip to main content
Glama

document_resync_source

Re-parse the document from its STORED source file and re-align blocks (unchanged blocks keep translations). The file owns sources: block_update edits are NOT in the file, so a resync overwrites them — resync when the source file changed, not after block edits.

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": {
      "document_id": "<document_id>"
    },
    "name": "document_resync_source"
  }
}

Input Schema

NameRequiredDescriptionDefault
document_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries the disclosure burden, and it does so for the most consequential trait: resync overwrites block_update edits because those edits never reach the file. It omits other behavioral context such as whether the re-parse runs as an async processing job, permission requirements, or failure modes when no source file is attached.

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?

Two sentences, zero waste, with the core action front-loaded and the destructive caveat immediately following. Nothing repeats the name or title and every clause carries information.

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 single-parameter tool with no annotations or output schema, the description covers purpose, selection criteria, and data-loss semantics adequately. Remaining gaps are secondary: async/job behavior and what happens to blocks that no longer align after the source change.

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?

Only one parameter (document_id) and schema description coverage is 0%, so the schema adds no meaning. The description refers to 'the document' and 'its STORED source file' but never states that a document_id identifier is supplied or what form it takes, leaving modest ambiguity.

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 (re-parse, re-align) on a specific resource (the document's STORED source file) and immediately adds the key semantic detail that unchanged blocks keep translations. It also implicitly distinguishes itself from block_update by noting that block edits live elsewhere.

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?

Gives explicit when/when-not guidance: resync when the source file changed, not after block edits. It names the alternative path (block_update) and the condition that selects each, so an agent can route without inference.

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