Skip to main content
Glama

strings_reimport

Re-submit the WHOLE current corpus against an existing master: the server diffs by unit id and answers with {units, versions[], delta_block_ids} — pass delta_block_ids VERBATIM as group_run_start.block_ids to run only the delta. Unchanged units keep their translations. Synchronous, bills nothing.

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>",
      "document": "<document>"
    },
    "name": "strings_reimport"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentYes
document_idYes
overwrite_targetsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

No annotations are supplied, so the description carries the full burden and does so: it discloses the diff mechanism (by unit id), the preservation behavior (unchanged units keep their translations), the synchronous execution model, and the cost profile (bills nothing). It also names the response shape inline, which an agent otherwise could not know since there is no output schema.

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?

One dense paragraph that front-loads the action, then the mechanics, then the follow-up call and the cost/sync facts. Every clause carries information; nothing is filler.

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

Completeness3/5

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

The return shape is described, which is valuable given there is no output schema, and the downstream chaining is explained. But for a mutation tool with a nested free-form `document` payload and an undocumented `overwrite_targets` flag, an agent still cannot confidently construct the call or predict what gets overwritten.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, so the description must compensate and largely does not. It never explains what the `document` object must contain (nested, free-form additionalProperties) or what `overwrite_targets` does — a boolean whose default and effect on existing translations is left entirely ambiguous, which matters given the promise that unchanged units keep their translations.

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?

States a specific verb and resource: re-submit the whole current corpus against an existing master, diffed by unit id. The emphasis on WHOLE separates it conceptually from a partial import, though it never names a sibling tool to sharpen the contrast.

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?

Gives a concrete usage path: take the returned delta_block_ids and pass them VERBATIM as group_run_start.block_ids to run only the delta. That is real routing guidance to a sibling. It stops short of saying when to prefer strings_import or when a full re-submit is inappropriate.

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