Skip to main content
Glama

List interface locales

list_languages
Read-only

Use this tool to see all 77 North Dakota Fairytales interface locales, their text direction, and how many published resources exist in each product. Arabic, Urdu, Persian, and Pashto are RTL. A locale appears because it is registered. A count of zero means that product is not published in that locale.

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_languages"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint=false), so the description's real contribution is output semantics: which languages are RTL, why a locale is present ('registered'), and what a zero count means. That zero-count interpretation is genuinely useful context an agent cannot get from structured fields. It doesn't discuss ordering or response shape, keeping it below a 5.

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?

Four short sentences, front-loaded with the primary capability and followed by the interpretive details. Each sentence adds information (RTL set, registration rule, zero-count meaning) rather than repeating the name. Minor redundancy exists between 'see all 77 ... locales' and 'A locale appears because it is registered.'

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?

With no parameters, no output schema, and read-only annotations, the description covers what an agent needs: what is returned, how to read text direction, and how to interpret counts. The only gap is the concrete response shape (field names, ordering), which is a modest omission for a small static reference list.

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 takes no parameters, so the baseline of 4 applies; there is nothing for the description to mis-describe. The description correctly indicates the tool is unfiltered and returns all 77 locales, which matches the empty input schema.

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?

The description uses a clear verb ('see all ... interface locales') and names the exact resource plus the three returned attributes: text direction and published-resource counts per product. That distinguishes it from get_resource, search_resources, and list_products without naming a sibling. It stops just short of a 5 because it doesn't explicitly contrast itself with those lookups.

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?

'Use this tool to see...' restates the purpose rather than giving when-to-use guidance. There is no statement about when to choose this over list_products or search_resources, no prerequisite context, and no exclusions. The usage context is only implied by the returned fields.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources