Skip to main content
Glama

Propose a change to an entry

propose_entry_change
Idempotent

Propose a change for a reviewer to decide — for any entry you may propose to, including ones you could edit live; nothing changes until a person approves it. Give only what changes; null clears a field. native_name (with native_name_lang) proposes the name in its own script shown under the title. On an entry with no Wikidata item, bio proposes a person’s date of birth (and birth name and place of birth), each with its source. qid proposes linking the entry to a Wikidata item, or a different one (null: unlink it), with adopt naming the fields the item may manage (left out: the server’s default on a first link, unchanged on a re-point); only a reviewer with Manage entries may approve that. note tells the reviewer why. While your own proposal on the entry is still waiting, this change is added to it rather than filed beside it: the answer names that proposal, with folded: true. Audited. Dry run by default: it names the entries already on the item.

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": {
      "entry": "<entry>"
    },
    "name": "propose_entry_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
bioNoA person’s date of birth (and optionally birth name and place of birth), each with the address of a source that states it, on an entry with NO Wikidata item; null removes it. The page states it like an item’s facts: for a person only, and only while they are 18 or over. Refused on an entry with a QID, where only the item’s facts are said; linking an item later drops it. On an entry with no kind, saving them makes it a person, in the same revision.
qidNoThe Wikidata item to link the entry to, e.g. "Q42" (a different one re-points it); null unlinks it.
noteNoWhy you propose this, in plain words: posted as the proposal’s first comment, which the reviewer reads with it. At most 2,000 characters. Never an internal tracking ID (a backlog or ticket number); a VHID is fine.
adoptNoWith qid: the fields the item may manage; the rest are taken back by the site.
entryYesThe entry: its VHID (11 digits), its short name (as in verifiedhandles.org/<short>), or its Wikidata QID (Q42).
firstNoHandles to move to the front, in this order, each by its value (a masked email by its ref); the others keep their order after them. Each must be one of the entry’s handles (after add / remove); the entry then keeps its own order rather than the site’s.
shortNo
titleNo
dry_runNotrue (the default): write nothing — show the change and the exact request it would send. false: make the change.
galleryNoThe images after the lead: the whole ordered list of media ids, replacing the gallery; [] empties it. At most 5, each once, never the lead.
subtitleNo
add_handlesNo
clear_imageNotrue: take the lead image off. At most one of image_media_id, image_commons_token and clear_image.
descriptionNo
native_nameNoThe entry’s name in its own script, shown under the title (e.g. 川瀬智子 for Tomoko Kawase); "" or null removes it and its language code. Plain text, at most 200 characters. Setting it takes it from the Wikidata sync, which otherwise fills it from the item’s name in native language (P1559).
handle_orderNoEvery handle, in the order the entry should show them: exactly the entry’s handles after add_handles and remove_handles, each once (a masked email by its ref). To move a few to the front, use `first` instead.
image_media_idNoA new lead image already on the site (media_catalog, get_entry), or one you uploaded held for this proposal (upload_image or upload_image_from_url with hold: true): only its uploader may propose a held image, and the approval releases it.
remove_handlesNoHandles to take off, each by its value — or, for an email this key may not see (value null in get_entry’s editing.handles), by {platform_id: "email", ref}.
idempotency_keyNoOptional: a key you choose (1–255 printable ASCII, e.g. a UUID), sent as the write’s Idempotency-Key. Calling again with the same key and the same change within 24 hours answers the first call’s result (replayed: true) and writes nothing; the same key with another change is refused (422).
takeover_fieldsNoFields to take back from the Wikidata sync, keeping their values.
base_revision_idNoThe revision you read (get_entry → editing.baseRevisionId). If the entry has changed since, the edit is refused as a conflict. Left out, the current revision is used.
native_name_langNoThe language code of native_name, as Wikidata writes it ("ja", "zh-hant", "ko"); null for none.
takeover_handlesNoHandles to take back from the Wikidata sync.
relinquish_fieldsNoFields to hand to the Wikidata sync.
relinquish_handlesNoHandles to hand to the Wikidata sync; only while Wikidata lists the value.
image_commons_tokenNoA new lead image from Wikimedia Commons: a hit’s `token` from search_commons_images. The file is recorded on the site first, as the editor’s picker does.
release_held_handlesNoHeld-back handles the sync may add back.
credit_wikipedia_pageNoCredit the description “from Wikipedia”: an English Wikipedia article or draft, by title ("Draft:Dominic McLaughlin") or address. The server reads the page (redirects followed) and refuses it unless at least half of the description’s three-word phrases are the page’s lead (credit_text_differs, with the share).
remove_wikipedia_creditNotrue: remove the “from Wikipedia” credit from the description.
credit_let_wikidata_manageNoWith a draft named in credit_wikipedia_page: false keeps the description site-authored. By default a draft’s credit hands the description to the Wikidata sync, which leaves it alone until the draft is an article linked from the entry’s Wikidata item.

Output Schema

NameRequiredDescriptionDefault
noteNoA dry run: what to do next to make the change, in words.
resultNoA real run: the route’s own answer, where the tool adds facts of its own beside it.
confirmNoA dry run of a change that needs it: the exact target to send back as `confirm` with dry_run: false.
dry_runNotrue: a dry run, which wrote nothing. Absent from a real run.
replayedNoA real run with an idempotency_key already used for this change: the first call’s answer, given back; nothing was written now.
would_sendNoA dry run: the exact request the real run would send (`method`, `path`, any `headers` such as an Idempotency-Key, and its `body`, `form` or `query`), or the requests, in order.
may_edit_liveNoA dry run of a live edit: whether this key’s account may edit this entry live.
refused_becauseNoA dry run the real run would be refused for: why, in words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / bio / description
      Previous value: -"A person’s date of birth (and optionally birth name and place of birth), each with the address of a source that states it, on an entry with NO Wikidata item; null removes it. The page states it like an item’s facts: for a person only, and only while they are 18 or over. Refused on an entry with a QID, where only the item’s facts are said; linking an item later drops it."New value: +"A person’s date of birth (and optionally birth name and place of birth), each with the address of a source that states it, on an entry with NO Wikidata item; null removes it. The page states it like an item’s facts: for a person only, and only while they are 18 or over. Refused on an entry with a QID, where only the item’s facts are said; linking an item later drops it. On an entry with no kind, saving them makes it a person, in the same revision."
    • addedInput schema / properties / native_name
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 200,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "The entry’s name in its own script, shown under the title (e.g. 川瀬智子 for Tomoko Kawase); \"\" or null removes it and its language code. Plain text, at most 200 characters. Setting it takes it from the Wikidata sync, which otherwise fills it from the item’s name in native language (P1559)."
      +}
    • addedInput schema / properties / native_name_lang
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 35,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "The language code of native_name, as Wikidata writes it (\"ja\", \"zh-hant\", \"ko\"); null for none."
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / first
      Added value: +{
      +  "description": "Handles to move to the front, in this order, each by its value (a masked email by its ref); the others keep their order after them. Each must be one of the entry’s handles (after add / remove); the entry then keeps its own order rather than the site’s.",
      +  "items": {
      +    "anyOf": [
      +      {
      +        "properties": {
      +          "platform_id": {
      +            "description": "The platform id, e.g. \"twitter\": one the platform catalog has (get_entry with include_platforms lists the enabled ones; platform_catalog, every one). A new handle on an unknown or disabled platform is refused (400 invalid_platform).",
      +            "minLength": 1,
      +            "type": "string"
      +          },
      +          "value": {
      +            "description": "The handle as stored, e.g. \"nasa\".",
      +            "minLength": 1,
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "platform_id",
      +          "value"
      +        ],
      +        "type": "object"
      +      },
      +      {
      +        "properties": {
      +          "platform_id": {
      +            "description": "The masked handle’s platform: \"email\".",
      +            "minLength": 1,
      +            "type": "string"
      +          },
      +          "ref": {
      +            "description": "A masked handle’s `ref` (get_entry → editing.handles, where its value is null): it names the stored handle without its address.",
      +            "pattern": "^[0-9]{1,18}$",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "platform_id",
      +          "ref"
      +        ],
      +        "type": "object"
      +      }
      +    ]
      +  },
      +  "maxItems": 50,
      +  "minItems": 1,
      +  "type": "array"
      +}
    • changedInput schema / properties / handle_order / description
      Previous value: -"Every handle, in the order the entry should show them: exactly the entry’s handles after add_handles and remove_handles, each once (a masked email by its ref)."New value: +"Every handle, in the order the entry should show them: exactly the entry’s handles after add_handles and remove_handles, each once (a masked email by its ref). To move a few to the front, use `first` instead."
  3. Changed1 schema field changed
    • addedInput schema / properties / bio
      Added value: +{
      +  "anyOf": [
      +    {
      +      "properties": {
      +        "birth_date": {
      +          "description": "The date of birth at the precision the source gives: \"2004-10-21\", \"2004-10\" or \"2004\".",
      +          "type": "string"
      +        },
      +        "birth_date_source": {
      +          "description": "The web address (http or https) of a source that states the date of birth.",
      +          "maxLength": 2048,
      +          "type": "string"
      +        },
      +        "birth_name": {
      +          "description": "The birth name, when the source gives one that is not the entry’s name.",
      +          "maxLength": 120,
      +          "type": "string"
      +        },
      +        "birth_name_source": {
      +          "description": "The address of a source that states the birth name (required with it).",
      +          "maxLength": 2048,
      +          "type": "string"
      +        },
      +        "birth_place": {
      +          "description": "The place of birth, as a reader would name it (\"Austin, Texas\").",
      +          "maxLength": 200,
      +          "type": "string"
      +        },
      +        "birth_place_source": {
      +          "description": "The address of a source that states the place of birth (required with it).",
      +          "maxLength": 2048,
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "birth_date",
      +        "birth_date_source"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "A person’s date of birth (and optionally birth name and place of birth), each with the address of a source that states it, on an entry with NO Wikidata item; null removes it. The page states it like an item’s facts: for a person only, and only while they are 18 or over. Refused on an entry with a QID, where only the item’s facts are said; linking an item later drops it."
      +}
  4. Added

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations, it discloses substantial behavior: proposals are reviewed and audited, nothing changes before approval, dry run is the default, changes fold into an existing waiting proposal with folded: true, bio is refused on entries with a QID, and linking a QID later drops bio. It also notes that approving a qid change requires Manage entries and explains native_name sync interaction.

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 dense and long, but the core concept is front-loaded and the clauses are purposeful for a 30-parameter tool. The folding behavior and dry-run default are important to surface early, and I did not find significant redundant wording.

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 a complex 30-parameter proposal tool with annotations and an output schema, the description covers the essential conceptual model: review-before-write, dry run, folding, bio restrictions, QID linking, and native_name behavior. Some parameter families such as handles, gallery, image, and Wikipedia credit are left to the rich schema, which is reasonable but leaves minor room for a higher completeness score.

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 already high at 83%, so the baseline is 3, but the description adds meaningful semantics for key fields: native_name with native_name_lang, bio on entries without Wikidata items, qid linking/unlinking and adopt, note as the reviewer-facing reason, and null clearing a field. It does not summarize every parameter family such as handles or gallery, but it adds useful conceptual guidance beyond the schema.

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 opens with a specific verb and resource: "Propose a change for a reviewer to decide" and clarifies it applies to "any entry you may propose to, including ones you could edit live." That distinguishes it from live-edit tools, but it does not explicitly differentiate it from nearby proposal siblings such as propose_entry_changes or propose_entry_revert.

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?

It gives clear usage context: use this when you want a reviewer to decide and nothing should change until a person approves, even on entries you could edit directly. It does not name when to choose a different proposal tool or give explicit exclusions beyond that operational distinction.

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.