Skip to main content
Glama
Sign In

Deepl

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Glossary Language Pairs

glossary_language_pairs
Read-onlyIdempotent

Supported glossary language pairs.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
supported_languagesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedOutput schema / properties / count
      Removed value: -{
-  "description": "Number of items returned.",
-  "type": "integer"
-}
    • removedOutput schema / properties / items
      Removed value: -{
-  "description": "List of supported glossary language pairs",
-  "items": {
-    "properties": {
-      "source_lang": {
-        "description": "Source language code",
-        "type": "string"
-      },
-      "target_lang": {
-        "description": "Target language code",
-        "type": "string"
-      }
-    },
-    "required": [
-      "source_lang",
-      "target_lang"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}
    • addedOutput schema / properties / supported_languages
      Added value: +{
+  "items": {
+    "properties": {
+      "source_lang": {
+        "type": "string"
+      },
+      "target_lang": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • removedOutput schema / required
      Removed value: -[
-  "items",
-  "count"
-]
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {}
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of items returned.",
+      "type": "integer"
+    },
+    "items": {
+      "description": "List of supported glossary language pairs",
+      "items": {
+        "properties": {
+          "source_lang": {
+            "description": "Source language code",
+            "type": "string"
+          },
+          "target_lang": {
+            "description": "Target language code",
+            "type": "string"
+          }
+        },
+        "required": [
+          "source_lang",
+          "target_lang"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items",
+    "count"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is clear. The description adds only the word 'supported', implying a constraint, but does not disclose whether it returns all pairs or how pairs are structured. It neither contradicts nor significantly enriches the 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?

The description is extremely concise, using only five words. It avoids waste and is easy to parse, though it is arguably too terse to convey full meaning.

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

Completeness2/5

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

Despite having an output schema and strong annotations, the description provides almost no context. It does not clarify the tool's role in glossary management, what a 'pair' means, or how it relates to sibling tools, leaving the agent without enough information to confidently select it.

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 the description carries no parameter burden. Baseline 4 is appropriate for parameterless tools, even though the description adds no parameter-specific information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource 'glossary language pairs' but lacks an explicit verb like 'list' or 'return', making the action ambiguous. It does not distinguish itself from sibling tools such as source_languages or target_languages.

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?

No guidance is given on when to use this tool versus alternatives. It does not mention use cases, context, or relationship to similar tools like source_languages or target_languages.

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

All Deepl 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