Skip to main content
Glama
Sign In
skill-ninja-mcp-server

skill-ninja-mcp-server

by aktsmm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

skillNinja_localize

Translate or localize skill descriptions in the index by providing the skill name and optional English or Japanese text.

Instructions

Translate/localize skill descriptions in the index. Provide skillName and description_en and/or description_ja. / スキル説明を翻訳・ローカライズ

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": {
      "skillName": "<skillName>"
    },
    "name": "skillNinja_localize"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceNoOptional source key for disambiguation when multiple skills share the same name
skillNameYesName of the skill to localize
description_enNoEnglish description for the skill
description_jaNoJapanese description for the skill (日本語の説明)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.4
    • addedInput schema / properties / source
      Added value: +{
+  "description": "Optional source key for disambiguation when multiple skills share the same name",
+  "type": "string"
+}
  2. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided, so the description should disclose behavioral traits. It only states that it translates/localizes, but does not specify if it overwrites existing descriptions, requires special permissions, or has side effects on other languages.

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?

The description is short and front-loaded with the action. Including both English and Japanese is useful for bilingual context, but could be slightly tighter by omitting the Japanese repetition.

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?

For a tool with 4 parameters and no output schema, the description lacks details on edge cases, overwrite behavior, and expected return value. It does not fully compensate for the absence of annotations.

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 coverage is 100%, so baseline is 3. The description reiterates the parameter names ('Provide skillName and description_en and/or description_ja') but adds no additional meaning about constraints, format, or behavior when both are provided.

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 clearly states the verb (translate/localize) and resource (skill descriptions in the index), and it is distinct from sibling tools like search, install, or webSearch.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. The description does not mention conditions, prerequisites, or when to prefer this over other tools like skillNinja_updateIndex.

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