Skip to main content
Glama
Sign In
Djelia MCP Server

Djelia MCP Server

Official
by djelia-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_supported_languages

Retrieve the list of languages supported by Djelia translation, including language codes and names for easy selection.

Instructions

List languages supported by Djelia translation.

Returns a list of {"code": str, "name": str}. Codes: bam_Latn (Bambara), fra_Latn (French), eng_Latn (English).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_supported_languages"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are present, so the description carries full burden. It discloses the return shape (list of {'code','name'}) and provides exact codes and names, which is concrete behavioral information. It omits error handling and auth, but that is acceptable for a simple read-only listing.

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?

Two short sentences: first states the purpose plainly, second provides return format and examples. No wasted words; fully front-loaded.

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

Completeness5/5

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

For a zero-parameter tool with an output schema, the description fully covers the purpose and return shape. Nothing is missing for an agent to call it correctly; the examples make the output concrete.

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

Parameters4/5

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

The tool has zero parameters, so baseline is 4. The description adds no parameter info because none is needed; the schema already shows no properties.

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?

Description uses specific verb 'List' and resource 'languages supported by Djelia translation', distinguishing it from siblings (translate, transcribe, text-to-speech) as a discovery tool. The purpose is unambiguous.

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?

Clear context: use this to see which language codes/names are available for translation. It does not explicitly state alternatives or when-not-to-use, but sibling tools are obviously different, so usage intent is clear.

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