Skip to main content
Glama

Update registry embed

update_registry_embed
Destructive

Change a term's, a claim's or a set's link on other sites (PM-1168) — the sites that may show it, its term — keeping the link, so the sites that have it keep working; for a set also its name, and its 'terms' or 'claims', each given replacing that part of the list (a term on it you may not open stays on it); and 'lang', the language it shows the words in. Only what you pass changes: an empty 'sites' allows any site, days 0 removes the term. Only for somebody who may write in the project; a line in its history.

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": {
      "embedId": "<embedId>"
    },
    "name": "update_registry_embed"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoA new term in days from now; 0 is until it is removed.
langNoThe language the link shows the words in, e.g. 'en' (PM-1373); empty shows them as written again.
sitesNoSites that may show it, comma-separated; empty is any site.
termsNoA set's terms, comma-separated, replacing its terms.
titleNoA set's new name.
claimsNoA set's claims, comma-separated, replacing its claims.
embedIdYesThe embed's id, from list_registry_embeds or a create_*_embed.
askedLangsNoThe languages kept translated besides, comma-separated (those pages of the link's sites asked for are added by themselves); replaces the list, empty clears it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / askedLangs
      Added value: +{
      +  "default": null,
      +  "description": "The languages kept translated besides, comma-separated (those pages of the link's sites asked for are added by themselves); replaces the list, empty clears it.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / lang
      Added value: +{
      +  "default": null,
      +  "description": "The language the link shows the words in, e.g. 'en' (PM-1373); empty shows them as written again.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds real behavioral detail beyond them: partial-update semantics, that the link itself is preserved, that empty 'sites' widens to any site, that days 0 removes the term, that a term you cannot open stays on the list, the write-permission requirement, and a history entry being written. Only the lack of any note on failure/return behavior keeps it from 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the body is a single sprawling sentence riddled with semicolons, parenthetical ticket references (PM-1168, PM-1373), and nested clauses that make it hard to parse. Information is present but the structure works against quick scanning.

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?

For an 8-parameter mutation with full schema coverage, no output schema, and destructive annotations, the description covers the essentials: partial-update behavior, sentinel values, permission requirements, and side effects. What remains unstated (error behavior, whether the embed key changes) is minor.

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%, so baseline would be 3, but the description adds interpretive value: empty 'sites' means any site, days 0 removes the term, list-style params replace that part of the list rather than append, and 'lang' controls display language. The 'askedLangs' semantics are left entirely to the schema, which is the main gap.

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 gives a specific verb (change) and resource (a term's, claim's or set's link on other sites), and the phrase 'keeping the link, so the sites that have it keep working' implicitly distinguishes it from create_*_embed and delete_registry_embed. It does not name a sibling outright, and the dense clause structure obscures the core purpose somewhat, so it stops short of a 5.

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 supplies meaningful usage context: 'Only what you pass changes', the empty-'sites' and days-0 conventions, and 'Only for somebody who may write in the project'. However, it never states when to reach for this tool versus delete_registry_embed or update_wiki_embed; that routing is left to inference.

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