Skip to main content
Glama

Update saved layout

update_schema
DestructiveIdempotent

Update a saved layout's display name and/or definition. A layout is {"type":"object","properties":{...}}. Each property is {"type":T} where T is one of any, null, boolean, string, number, date, array, object. An optional description, at most 400 characters, tells the model how to read that key. An optional required array lists the keys that must be present. A date is a string yyyy-mm-dd. An array adds "items" (one node). An object adds "properties" and may add "required". At most 4 levels below the root, 100 keys, and 16384 bytes.

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": {
      "slug": "<slug>"
    },
    "name": "update_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoLabel shown in the console. Letters, digits, spaces, underscore, hyphen.
slugYesThe current slug (URL path identifies this row).
schemaNoA layout is {"type":"object","properties":{...}}. Each property is {"type":T} where T is one of any, null, boolean, string, number, date, array, object. An optional description, at most 400 characters, tells the model how to read that key. An optional required array lists the keys that must be present. A date is a string yyyy-mm-dd. An array adds "items" (one node). An object adds "properties" and may add "required". At most 4 levels below the root, 100 keys, and 16384 bytes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"The current name."New value: +"Label shown in the console. Letters, digits, spaces, underscore, hyphen."
    • removedInput schema / properties / name / pattern
      Removed value: -"^[a-z0-9_-]+$"
    • removedInput schema / properties / newName
      Removed value: -{
      -  "description": "Lowercase letters, digits, underscores, and hyphens. No spaces.",
      -  "maxLength": 80,
      -  "minLength": 1,
      -  "pattern": "^[a-z0-9_-]+$",
      -  "type": "string"
      -}
    • changedInput schema / properties / schema / description
      Previous value: -"A schema is {\"type\":\"object\",\"properties\":{...}}. Each property is {\"type\":T} where T is one of any, null, boolean, string, number, date, array, object. An optional description, at most 400 characters, tells the model how to read that field. An optional required array lists the keys that must be present. A date is a string yyyy-mm-dd. An array adds \"items\" (one node). An object adds \"properties\" and may add \"required\". At most 4 levels below the root, 100 keys, and 16384 bytes."New value: +"A layout is {\"type\":\"object\",\"properties\":{...}}. Each property is {\"type\":T} where T is one of any, null, boolean, string, number, date, array, object. An optional description, at most 400 characters, tells the model how to read that key. An optional required array lists the keys that must be present. A date is a string yyyy-mm-dd. An array adds \"items\" (one node). An object adds \"properties\" and may add \"required\". At most 4 levels below the root, 100 keys, and 16384 bytes."
    • addedInput schema / properties / slug
      Added value: +{
      +  "description": "The current slug (URL path identifies this row).",
      +  "maxLength": 80,
      +  "minLength": 1,
      +  "pattern": "^[a-z0-9_-]+$",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "name"
      -]New value: +[
      +  "slug"
      +]
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations declare destructiveHint=true and idempotentHint=true, so the safety profile is already covered. What the description never resolves is the critical mutation question: whether supplying 'schema' replaces the entire stored definition or merges with it, and what happens to the existing layout if a field is omitted. Those constraints, such as depth, key count, and byte caps, restate validation already present in the schema.

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 sentence is properly front-loaded, but the remaining bulk is a dense grammar specification copied verbatim from the schema's description field. Hinting that 'date is a string yyyy-mm-dd' and the limits are useful, yet the repetition pads the definition without changing what the agent learns.

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, idempotent update with a nested object parameter, the grammar is well covered. Missing are the operational semantics: replace versus merge behavior, whether omitting 'name' preserves it, and what happens when the slug does not resolve to an existing layout.

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 all three parameters are documented in structured form, including the name format, the slug pattern, and the layout grammar. The description largely duplicates the schema field's own text rather than adding new meaning, so the baseline of 3 applies.

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 first sentence gives a specific verb and resource: 'Update a saved layout's display name and/or definition.' It also clarifies that 'schema' means the layout definition, which reconciles the tool name with the domain language. It does not, however, frame the tool against siblings like create_schema or get_schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to call this versus create_schema, get_schema, or list_schemas, and no stated prerequisites such as the layout must already exist. The word 'saved' and the required slug field imply an existing row must be targeted, but the agent must infer that.

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