Skip to main content
Glama

Approve reconfigurations

approve_reconfigurations
Destructive

An administrator's word that one week may have more reconfigurations than the ceiling: up to 'count', or as many as it has now. Every later write of that week — a bot's too — is held to it. Only somebody who configures the project.

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>",
      "week": "<week>"
    },
    "name": "approve_reconfigurations"
  }
}

Input Schema

NameRequiredDescriptionDefault
weekYesAny day of the week, YYYY-MM-DD; the week runs Monday to Sunday.
countNoHow many it may have. Leave out for as many as it has now.
reasonNoWhy — 'premiere week'.
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 destructiveHint=true and readOnlyHint=false, so the write semantics are covered. The description does add meaningful context beyond them: the approval persists and binds 'every later write of that week — a bot's too', which tells the agent the effect outlives the call and applies to non-human actors. It does not say whether the approval can be revoked, what happens if count is below the current usage, or what the call returns.

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?

Three short sentences with no filler, and the persistence constraint is placed early. However, the figurative opening ('An administrator's word that one week may have more reconfigurations than the ceiling') delays the actual operation, which is never stated in plain terms.

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, persistent mutation with no output schema, the description covers effect, scope and authorisation reasonably well. It leaves gaps on reversibility, on behaviour when count is below current usage, and on failure modes, which matter more here than for a read tool.

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%, so week, count, reason and project are all documented in the schema itself, including the Monday-to-Sunday week rule and the null-count default. The description only restates the count default in prose ('up to count, or as many as it has now') and adds no format, range, or validation detail beyond 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 conveys a specific action on a specific resource: an administrator raises the per-week ceiling on reconfigurations to a given count (or the current amount) for one week. It is distinguishable from the sibling list_reconfigurations, though the phrasing 'an administrator's word' is metaphorical and never plainly states 'set/raise the weekly reconfiguration limit'.

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?

The only guidance is an eligibility restriction ('Only somebody who configures the project'), which is a prerequisite, not a when-to-use rule. There is no statement of when to choose this over list_reconfigurations or when the ceiling needs approving at all, and no exclusion cases (e.g. lowering a ceiling, weeks already approved).

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