Skip to main content
Glama

Remont — renovation planner

Get UI labels

get_ui_labels
Read-only

English widget texts (form and plan). Translate the values into the user's language and pass them as labels.

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

Input Schema

NameRequiredDescriptionDefault
localeNoLanguage code you translate into (e.g. lt, fr, ja) — for statistics

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds a genuinely non-obvious behavior: the returned texts are always English and translation is the caller's responsibility, which an agent could not infer from the schema or annotations.

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 short sentences with no filler, and the resource identification is front-loaded. The phrasing is slightly telegraphic ("(form and plan)"), but nothing is wasted.

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

Completeness3/5

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

There is no output schema, and the description never says what the return value looks like — presumably a key/text mapping to be passed as labels, but that is left to inference. For a simple one-parameter read tool this is close to adequate, but the return shape is the main gap.

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?

Schema coverage is 100% and the schema itself explains locale as being "for statistics." The description reinforces this by framing translation as something the agent performs rather than something the tool does, clarifying that locale does not change the output language — meaning added beyond the schema field.

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 names a concrete resource — English widget texts for forms and plans — and implies retrieval, which is enough to distinguish it from the plan/catalog/profile siblings. It is not a tautology of the name, but the verb is implicit ("get" only appears in the name) and the parenthetical "(form and plan)" is terse.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives post-call guidance — translate the returned values into the user's language and pass them as labels — which tells the agent what to do with the result. It does not state when to call this versus other tools, nor any prerequisites or exclusions, so usage is only implied.

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