Skip to main content
Glama

Get layout settings

get_layout_settings
Read-only

How a project's reconfigurations are planned: 'weeklyCeiling' (at most so many a week without an administrator's word; null for none), 'requiredRoles' (team roles somebody on it has to hold — 'only with an electrician'), 'excludedRoles' (roles nobody on it may hold), and 'approvals' — weeks allowed over the ceiling. Any member may read.

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": "get_layout_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYesThe project key, e.g. TH.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the access rule ('Any member may read') and by defining the semantics of each returned field, including null meaning for weeklyCeiling. It stops short of covering null/default behavior for the other fields or what is returned when a project has no layout configured.

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?

One dense sentence with no wasted words; the field semantics are front-loaded and each definition earns its place. It is a sentence fragment rather than a statement with a verb, which costs a little clarity but nothing in length.

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 no output schema, the description carries the burden of explaining return values, and it does so field by field for a four-field settings object. The main residual gap is what happens for projects where these settings are absent or partially unset beyond weeklyCeiling's null case.

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 100% and the single 'project' parameter already carries an example ('TH'), so the schema does the work. The description adds no additional meaning about the project key, 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 description names the resource precisely and enumerates the exact fields it exposes (weeklyCeiling, requiredRoles, excludedRoles, approvals), so an agent knows what it will get back. It never uses an explicit verb like 'returns' — it reads as a fragment ('How a project's reconfigurations are planned') — but combined with the name the intent is unambiguous.

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 statement of when to call this versus set_layout_settings, which is the obvious write counterpart in the sibling list, nor any prerequisite or exclusion. The only routing-adjacent sentence is a permission note ('Any member may read'), which tells the agent who can call it, not when to.

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