Skip to main content
Glama
Sign In
MCP Arabic Toolkit

MCP Arabic Toolkit

by seotarek
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

arabic_strip_diacritics

Removes Arabic diacritics (Tashkeel/Harakat) and Tatweel from text, returning normalized plain Arabic for search, comparison, or processing.

Instructions

Removes all vowel marks (Tashkeel/Harakat) and elongation (Tatweel) from Arabic text.

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": {
      "text": "<text>"
    },
    "name": "arabic_strip_diacritics"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe Arabic text with diacritics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does specify the exact categories removed, which is real behavioral content, but says nothing about whether the input is mutated or a new string returned, and whether stripping is lossless/irreversible.

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 sentence, front-loaded with the verb, and zero filler. Nothing could be removed without losing 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 one-parameter pure text transform with no output schema, the description is nearly sufficient. Only minor gaps remain, such as what the returned value looks like when no diacritics are present.

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?

Single required parameter with 100% schema coverage, so the schema fully documents the input type and meaning. The description adds no format or edge-case detail beyond the schema, which is the baseline for full coverage.

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 ('Removes') and precise resource ('vowel marks (Tashkeel/Harakat) and elongation (Tatweel)'), with the Arabic script terminology disambiguating exactly what is stripped. It does not distinguish itself from the sibling arabic_normalize_text, which plausibly also removes diacritics as part of normalization.

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 statement of when to prefer this over arabic_normalize_text, nor any precondition or exclusion. Usage is only implied by the operation name itself, so the agent must guess the boundary with the sibling normalizer.

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