Skip to main content
Glama

put_menu_doc

DestructiveIdempotent

Replace the whole menu doc (ifMatch from get_menu_doc required). Each item may omit menu — the enclosing menu key in doc is used.

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": {
      "site": "<site>",
      "doc": "<doc>",
      "ifMatch": "<ifMatch>"
    },
    "name": "put_menu_doc"
  }
}

Input Schema

NameRequiredDescriptionDefault
docYes
siteYesSite slug, e.g. acme-studio
contextNoWhy you're calling this (activity log).
ifMatchYesWhole-doc etag from get_menu_doc. Required (sent as If-Match).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / context / description
      Previous value: -"Optional: one sentence on why you are calling this (shown in the site's activity log; no personal data)."New value: +"Why you're calling this (activity log)."
  2. Changed3 schema fields changed
    • changedInput schema / properties / context / description
      Previous value: -"One sentence: why you are calling this tool and what you are trying to accomplish. Stored on the site's activity log and visible to everyone on the site — never put secrets or personal data here."New value: +"Optional: one sentence on why you are calling this (shown in the site's activity log; no personal data)."
    • removedInput schema / properties / guestToken
      Removed value: -{
      -  "description": "Guest token from start_site. Send it on every call until claim_site. Omit when this chat is already signed in to Dotsy.",
      -  "minLength": 20,
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "site",
      -  "doc",
      -  "ifMatch",
      -  "context"
      -]New value: +[
      +  "site",
      +  "doc",
      +  "ifMatch"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / doc / additionalProperties / properties / items / items / required
      Previous value: -[
      -  "sort",
      -  "parent",
      -  "label",
      -  "kind",
      -  "ref",
      -  "id",
      -  "menu"
      -]New value: +[
      +  "sort",
      +  "parent",
      +  "label",
      +  "kind",
      +  "ref",
      +  "id"
      +]
  4. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint/idempotentHint, so the safety profile is covered. The description adds genuinely new behavioral context: the operation is a wholesale replacement (so omitted items are gone) and it requires an optimistic-concurrency etag obtained from get_menu_doc, which the annotations never mention.

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?

Two short sentences, front-loaded with the replacement semantics and no filler. The trailing clause is elliptical ('the enclosing menu key in doc is used') and costs a little clarity for its terseness.

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 destructive, nested-object mutation with no output schema, the description leaves notable gaps: it does not say that items absent from the payload are deleted, nor whether a fresh etag is returned for chaining further writes. The core contract is present but thin given the tool's complexity.

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 coverage is 75% and the undocumented parameter is the deeply nested 'doc', which carries almost all the semantic weight. The description contributes one valuable rule not in the schema — an item may omit 'menu' and inherit the enclosing key — but says nothing about shell/template, ordering by 'sort', or parent/id relationships.

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?

States a specific verb+resource: 'Replace the whole menu doc', which contrasts implicitly with the single-item sibling put_menu_item and with reorder_menu. It does not name a sibling outright, so differentiation relies on the 'whole doc' vs 'item' distinction.

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?

The parenthetical '(ifMatch from get_menu_doc required)' establishes the read-then-write prerequisite, which is useful workflow guidance. However, there is no explicit statement of when to prefer this over put_menu_item, delete_menu_item, or reorder_menu for partial edits.

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