Skip to main content
Glama
Sign In
timps-swarm

timps-swarm

by Sandeeprdy1729
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

timps_i18n_agent

Extracts translatable strings from source code, generates translation JSON for multiple locales, and flags RTL/cultural issues.

Instructions

Extract translatable strings from source code, generate translation JSON files for multiple locales, and flag RTL/cultural issues.

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": {
      "code": "<code>"
    },
    "name": "timps_i18n_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesSource code to scan
source_localeNoen
i18n_frameworkNoauto
target_localesNoe.g. ['fr', 'de', 'ja', 'ar']

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.1

TDQS

C2.9/5.0
Behavior3/5

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

The description clearly states the tool extracts strings, generates JSON files, and flags issues, which is transparent about its primary actions. However, it does not disclose any potential side effects such as file overwriting, network calls, or limitations.

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 description is a single, clear sentence listing the three main actions. It is concise and well-structured without unnecessary words.

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

Completeness2/5

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

The description gives an overview of functionality but omits details on input expectations, output format, or return values. Since there is no output schema, the agent may not know what results to expect, making it incomplete.

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

Parameters1/5

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

The tool description does not elaborate on the meaning or role of any of the four parameters. It only mentions 'multiple locales' without connecting to target_locales, and the schema descriptions are equally minimal, so the description adds no additional parameter context.

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 precisely states the tool's purpose: extracting translatable strings, generating translation JSON files for multiple locales, and flagging RTL/cultural issues. This is specific and easily distinguishes it from generic agents.

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

Usage Guidelines1/5

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

The description does not provide any guidance on when to use this tool compared to other agents. It simply states the tool's functions without context on appropriate scenarios or alternatives.

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

Deploy Server

Other Tools