Skip to main content
Glama

Replace metadata

set_metadata
Read-only

Replace the document metadata. Pass the complete metadata object; omitted fields are removed.

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": {
      "document": "<document>",
      "metadata": "<metadata>"
    },
    "name": "set_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentYesThe Publisle document: an object with schemaVersion and blocks, as returned by the other tools.
metadataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior1/5

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

The description claims a mutating replace operation ('Replace the document metadata', 'omitted fields are removed'), but the annotations declare readOnlyHint=true and destructiveHint=false. The removal semantics are exactly the kind of destructive behavior the annotations deny, so the description directly contradicts structured data.

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?

Two short sentences, front-loaded with the action and immediately followed by the critical replacement rule. There is no padding or redundant restatement of the tool name.

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

Completeness3/5

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

For a nested-object mutation tool with no output schema, the description covers the replacement contract well but says nothing about what keys the metadata object accepts, what permissions are needed, or what is returned. Those gaps are notable, and the incorrect annotations make the description the only reliable behavior source.

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 only 50%, and the metadata parameter has no schema description at all. The description compensates by defining replace semantics for it – the full object must be supplied and omitted fields are dropped – which is essential meaning the schema does not provide, while the document parameter is already covered in 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 uses a specific verb and resource, 'Replace the document metadata', which is unambiguous and matches the tool name. It does not name a sibling alternative, but no sibling in the list appears to touch metadata, so the distinct resource carries the differentiation.

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 clearly implies when to use it (when you want to set the document's metadata wholesale) and gives a strong invocation rule: pass the complete object. It does not say when not to use it, nor does it reference any alternative approach for partial metadata changes.

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