FarsiTools (paid)

fa_digits

Convert the digits inside a string between Persian (۰-۹), Arabic-Indic (٠-٩) and ASCII (0-9) numeral systems, leaving the rest of the text untouched. Use it to make Persian text machine-readable or to render an ASCII number in Persian script. Returns the converted string. ($0.003 per call, USDC on Base)

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": "fa_digits"
  }
}

Input Schema

Name	Required	Description	Default
`to`	No
`text`	Yes	text containing digits

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does well: it states only digits are altered ('leaving the rest of the text untouched'), discloses the return ('Returns the converted string'), and even surfaces cost/network. It omits any mention of permissions, rate limits beyond price, or what happens with mixed/unsupported digit sets.

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?

Three tight sentences, front-loaded with the core action, followed by use cases, return value, and pricing. No filler or redundancy.

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 simple, low-complexity conversion tool with no output schema, stating the return type is sufficient. The one real gap is the undefined 'to' value vocabulary, which leaves a small but meaningful unknown before invocation.

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 50% - 'text' is documented but 'to' has no description at all. The description names the three numeral systems but never specifies the accepted values for 'to' (e.g. 'en', 'fa', 'ar'), so the agent still cannot confidently construct that argument.

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?

States a specific verb (Convert) on a specific resource (digits inside a string) across three named numeral systems, and scopes it with 'leaving the rest of the text untouched'. An agent can immediately distinguish this from siblings like fa_normalize or fa_numberToWords.

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?

Provides two concrete use cases ('make Persian text machine-readable' and 'render an ASCII number in Persian script'), which gives clear context for when to reach for it. However, it names no alternatives or exclusions (e.g. when to use fa_normalize instead).

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

All FarsiTools (paid) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?