Skip to main content
Glama

Set layout settings

set_layout_settings
Destructive

Set how a project's reconfigurations are planned — the WHOLE of it as written: the weekly ceiling (leave out for none) and the team roles a reconfiguration asks for and keeps away, by id or name, 'a,b'. Only somebody who configures the project (its lead or an administrator).

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": {
      "project": "<project>"
    },
    "name": "set_layout_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYesThe project key, e.g. TH.
excludedRolesNoTeam roles nobody on it may hold, 'a,b'.
requiredRolesNoTeam roles somebody on a reconfiguration has to hold, 'a,b' — e.g. 'Electrician'.
weeklyCeilingNoAt most so many reconfigurations a week, 0-100. Leave out for no ceiling.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 meaningful context beyond them: 'the WHOLE of it as written' signals full-replacement semantics (omitted fields are cleared, e.g. weeklyCeiling 'leave out for none'), and it discloses the authorization requirement. It stops short of describing what the response looks like, but the replacement consequence and permission barrier are exactly the behavioral facts an agent needs.

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?

It is a single sentence and the key scope constraint is front-loaded, but the phrasing is convoluted ('the WHOLE of it as written', 'asks for and keeps away') and the permission note is tacked on as a trailing clause rather than structured clearly. The content earns its place; the wording could be tightened considerably.

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?

With four parameters, full schema coverage, and annotations carrying the safety profile, the description does most of what is needed: it states the effect, the replacement behavior, the value format, and the authorization requirement. Only the return/confirmation behavior is unaddressed, which is minor given no output schema.

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 the schema already defines all four parameters, setting the baseline at 3. The description still adds value by stating the 'a,b' format and 'by id or name' for roles and by clarifying that omission means none — reinforcing the replacement semantics that the schema's nullable defaults do not clearly convey.

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 names a specific verb ('Set') and a concrete resource ('a project's reconfigurations are planned'), then enumerates the settings being set (weekly ceiling, required/excluded roles). It does not explicitly differentiate from the sibling get_layout_settings, and the phrase 'the WHOLE of it as written' is unusual, but an agent can tell this is the write-side counterpart for layout settings.

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 gives a real precondition — 'Only somebody who configures the project (its lead or an administrator)' — which helps an agent decide whether the call will succeed. However, there is no explicit when-to-use/when-not guidance and no reference to alternatives (e.g. get_layout_settings to read first), so the usage context is only implied.

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