Skip to main content
Glama

Tjaz

by com.tjaz
OverviewDiscussionsAdmin

Translate a quiz on Tjaz

translate_quiz
Idempotent

Translates a quiz on Tjaz into another language and gives back the link to the translation. Takes up to a minute

Input Schema

NameRequiredDescriptionDefault
quizYesThe quiz's id or link
languageYesThe language to translate it into: the language's code as Tjaz has it, ISO 639-1, e.g. da, en, ar, uk, and nb for Norwegian

Output Schema

NameRequiredDescriptionDefault
quizNo
statusYes
messageNoWhy it was refused, or what to tell the user

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / quiz / properties / links / properties / team
      Added value: +{
+  "description": "Plays it on a big screen as one team against cute, silly monsters, everyone answering on their phone or laptop: the more answer right, the better the team defends, and each monster becomes its friend. Good for a class or a group of children",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedOutput schema / properties / quiz / properties / links / properties / bigScreen / description
      Previous value: -"Plays it together on a big screen, everyone answering on their phone"New value: +"Plays it together on a big screen, everyone playing along on their phone or laptop"
  3. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish that this is a non-destructive, idempotent, non-read-only operation. The description adds useful behavioral context beyond annotations by disclosing that the operation may take up to a minute and that it returns a link to the translation.

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?

The description is extremely concise and front-loaded: the purpose is stated first, followed by the useful latency note. Every clause contributes information without 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?

With a complete input schema, an output schema, and meaningful annotations, the description covers the core operation and adds a practical timing detail. It is sufficient for invocation, though it could mention any constraints on supported languages or quiz types.

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 description coverage is 100%, so both parameters are already fully documented in the schema. The description adds no additional parameter semantics beyond what the schema provides, which is acceptable at baseline 3.

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 states a specific verb and resource: it translates a quiz into another language and returns the translation link. The operation is clearly distinguishable from siblings like get_quiz or make_quiz, though it does not explicitly mention those alternatives.

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?

The description gives no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. The only contextual note is the expected duration, which is useful but not usage guidance.

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

All Tjaz toolsInspect
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