Skip to main content
Glama
Sign In

globalize.now

by io.github.globalize-now
OverviewDiscussionsAdmin

Delete a glossary entry

delete_glossary_entry
Destructive

Delete a single glossary entry by its id (from list_glossary) from a project in your organisation. Marks matching translation-memory entries stale so the affected content is re-translated without the removed term. A project's glossary may be shared by other projects and Workflows in the organisation: a change to it applies to every one of them, and only the terms of the languages of the addressed project are listed or changed. The result's glossary.sharedWith names the others — tell the user which ones a change affects. While glossary.repositoryManaged is set, the glossary is synced from that project's asset repository and every write is refused. When referring to a project or language in your reply to the user, use its name and locale (e.g. "French (fr-FR)") — ids (UUIDs) are for tool calls only, never show them to the user.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project": "<project>",
      "entryId": "<entryId>"
    },
    "name": "delete_glossary_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
entryIdYesThe glossary entry id to delete (from list_glossary)
projectYesProject id (UUID) or slug

Output Schema

NameRequiredDescriptionDefault
deletedYes
entryIdYes
glossaryYesThe project's attached glossary and what else uses it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / glossary
      Added value: +{
+  "additionalProperties": {},
+  "description": "The project's attached glossary and what else uses it",
+  "properties": {
+    "id": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "repositoryManaged": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "properties": {
+            "branch": {
+              "type": "string"
+            },
+            "gitUrl": {
+              "type": "string"
+            },
+            "projectId": {
+              "type": "string"
+            },
+            "repositoryId": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "projectId",
+            "repositoryId",
+            "gitUrl",
+            "branch"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "The project whose asset repository the glossary is synced from (writes are refused), or null"
+    },
+    "sharedWith": {
+      "additionalProperties": {},
+      "properties": {
+        "projects": {
+          "description": "Other projects attached to the glossary",
+          "items": {
+            "additionalProperties": {},
+            "properties": {
+              "id": {
+                "type": "string"
+              },
+              "name": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "id",
+              "name"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "workflows": {
+          "description": "Active Workflows using the glossary",
+          "items": {
+            "additionalProperties": {},
+            "properties": {
+              "id": {
+                "type": "string"
+              },
+              "name": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "id",
+              "name"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "projects",
+        "workflows"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "sharedWith",
+    "repositoryManaged"
+  ],
+  "type": "object"
+}
    • changedOutput schema / required
      Previous value: -[
-  "deleted",
-  "entryId"
-]New value: +[
+  "deleted",
+  "entryId",
+  "glossary"
+]
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, yet the description adds substantial non-obvious behavior: matching translation-memory entries are marked stale and content re-translated, the change propagates to other projects/workflows sharing the glossary, and writes are blocked under repositoryManaged. The sharedWith field and the instruction to surface it to the user is exactly the kind of side-effect disclosure an agent needs.

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 core action is front-loaded, followed by the consequences (stale TM entries, shared glossary) and the blocking condition, which is a sensible ordering. The final sentence about using names/locales instead of UUIDs is generic formatting boilerplate that slightly dilutes focus but is still operationally relevant to the reply.

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 two-parameter destructive delete with full schema coverage, a rich annotation set, and an output schema, the description covers everything an agent needs: provenance of the id, propagation scope, refusal condition, and what to report back. Nothing material is missing.

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 the schema already documents both entryId (with its UUID pattern and list_glossary provenance) and project (UUID or slug). The description reinforces the id's origin and the project/language scoping rule but adds no syntax or format detail beyond the schema. Baseline 3 applies.

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?

Opens with a specific verb+resource ("Delete a single glossary entry by its id") and scopes it to a project in the organisation. This clearly separates it from siblings like delete_style_guide, delete_translation_memory_entries, and list_glossary.

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?

Tells the agent where the id comes from (list_glossary) and states a real precondition: writes are refused while glossary.repositoryManaged is set. It also warns that the glossary may be shared and that only the addressed project's languages are changed, which guides correct invocation. No explicit "use X instead" alternative is given, but the context is clear.

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

All globalize.now 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