Yani – Emirati Arabic

Search Emirati phrases

search_phrases

Read-onlyIdempotent

Use this when the user asks how to say something in Emirati Arabic (the spoken dialect of the UAE, not formal Arabic), or wants Emirati phrases about a topic. Search in English, Easy Latin or Arabic. Returns up to 10 phrases, each with Arabic script, an easy Latin spelling, the English meaning, who it's said to when that matters, a real recording where there is one, and a link to its page.

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": {
      "query": "<query>"
    },
    "name": "search_phrases"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes	What to say, in English ("thank you"), Easy Latin or Arabic.

Output Schema

Name	Required	Description	Default
`phrases`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely new behavior: a hard cap of up to 10 results, accepted input languages, and the presence of audio recordings and page links, which tells the agent results may be partial or richly attributed.

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?

Two sentences, front-loaded with the trigger condition before the result summary, with no filler. The enumerated result fields are somewhat redundant given an output schema exists, which costs a point on efficiency.

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 two-parameter read-only search with an output schema, the description covers dialect scope, input formats and result limits — enough to call it correctly. The only gap is that the result-field enumeration duplicates what the output schema already provides rather than adding behavior such as ranking or empty-result handling.

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?

The query parameter already carries a schema description, and the description's 'Search in English, Easy Latin or Arabic' largely restates it. The undocumented limit parameter is only obliquely implied by 'Returns up to 10 phrases', so the 50% coverage gap is not fully compensated.

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?

Specific verb (search) plus resource (Emirati phrases), and it explicitly scopes the dialect as 'the spoken dialect of the UAE, not formal Arabic', which an agent could otherwise confuse. It also allows topical browsing as well as translation-style lookup.

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?

The opening clause gives a clear trigger condition ('when the user asks how to say something... or wants Emirati phrases about a topic'). It does not, however, tell the agent when to prefer get_phrase or list_situations over searching, leaving that routing to inference.

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

All Yani – Emirati Arabic 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?