Skip to main content
Glama

Remove a program rule

remove_program_rule
DestructiveIdempotent

Removes one of the custom program's own rules. Forks a preset first.

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": {
      "id": "<id>"
    },
    "name": "remove_program_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description does add one genuinely new behavioral fact — "Forks a preset first" — revealing a side effect (a preset is copied before removal), but it is too terse to explain what the fork means, whether it persists, or what happens if the rule belongs to a preset rather than a custom program.

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 action and followed by the side-effect caveat; nothing is wasted. The brevity edges toward under-specification rather than verbosity, but structurally it is clean.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a destructive mutation with no output schema and an undocumented required parameter, so the description carries most of the burden. It omits what the fork produces, whether removal is reversible, permission requirements, and how to obtain a valid rule id — significant gaps for a delete operation.

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?

There is a single required parameter (id) with 0% schema description coverage, so the schema contributes nothing about its meaning. The description only indirectly implies that id identifies a rule within the custom program; it gives no format, source, or lookup guidance for obtaining a valid id.

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 and resource ("Removes ... rules") and scopes it to "the custom program's own rules," which implicitly separates it from remove_athlete_rule and from the set_program_rule family. It stops short of naming a sibling explicitly, so differentiation is inferential rather than stated.

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 phrase "one of the custom program's own rules" implies the applicable context (program-level rules, not athlete rules), but there is no explicit when-to-use/when-not guidance and no mention of set_program_rule as the counterpart for adding or editing. Usage is implied rather than directed.

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