Skip to main content
Glama

strings_import

Import a Transept Strings corpus (.tstrings.json shape). Locales: explicit params win; with none named the corpus header target_locales apply (no locales anywhere → sync no_target_languages). A single-locale import is ONE version row carrying the corpus (language_group_id null until more locales join). Async: returns processing_job_id — poll processing_job_get. Translations the corpus carries land active and bill 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": "<document>"
    },
    "name": "strings_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentYes
project_idNo
target_languageNo
target_languagesNo
document_categoryNo
use_target_localesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses the async contract (returns processing_job_id, poll processing_job_get), the versioning model (single-locale import = one version row, language_group_id null until more locales join), and the billing side effect (carried translations land active and bill nothing). It omits auth requirements, error/failure behavior, and whether re-importing the same corpus duplicates or replaces rows.

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 purpose, then tight telegraphic sentences on locale precedence, versioning, async flow, and billing. Dense but every clause carries information; a few phrasings ('ONE version row', 'language_group_id null') are terse enough to need a second read.

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?

For a mutation/import tool with no annotations, no output schema, and six undocumented parameters, the description covers the operational essentials (async polling, locale resolution, billing) but is not complete enough: three parameters and the failure/duplicate-import semantics remain unaddressed.

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?

Schema description coverage is 0%, so the description must compensate and it only partly does. It clarifies document (the corpus shape) and the target_language/target_languages precedence, but leaves project_id, document_category, and use_target_locales unexplained, and does not state the maxItems 20 cap on target_languages.

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 ('Import a Transept Strings corpus') and pins the expected payload shape (.tstrings.json). It does not explicitly contrast with the sibling strings_reimport or tm_import, so the agent must infer the distinction, but the operation itself is unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives conditional behavior for the locale parameters (explicit params win, else corpus header target_locales, else sync no_target_languages) and tells the agent to poll processing_job_get after the async call. It stops short of saying when to choose this over strings_reimport or tm_import, which are the closest alternatives.

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