Skip to main content
Glama

Fix a quality profile

fix_profile
Destructive

Corrects unreachable-floor or knife-edge-floor quality profile issues by setting the minimum custom format score to the sum of positive formats minus the cheapest after re-check and preview.

Instructions

Applies a proven quality profile fix: for a certain unreachable_floor or knife_edge_floor finding from get_profile_issues, sets the profile's minimum custom format score to the total of its positive formats less the cheapest one, nothing else. Re-checks first, so a finding that no longer holds is refused, as is a profile on an instance where Profilarr syncs every profile (change it in Profilarr). The preview shows the old floor, which only a manual edit restores. Confirm to apply; returns the profile and both floors. Field reference: arr://docs/fix_profile.

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": {
      "service": "<service>",
      "profile": "<profile>",
      "finding": "<finding>"
    },
    "name": "fix_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoThe token from this tool's preview; pass it back to apply.
dry_runNoPreview only, no token issued: for "what if" questions, not the first step of a change.
findingYesThe finding's `kind`.
profileYesThe profile, by the name get_profile_issues printed (an id also works).
serviceYes
instanceNoWhich instance (e.g. "4k") when several of this service exist. Omit it when there is one.

Output Schema

NameRequiredDescriptionDefault
noopYes
tierYes
toolYes
targetYes
appliedYes
dry_runYes
effectsYes
serviceYes
summaryYes
operationYes
permissionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv2.2.0
    • changedInput schema / properties / confirm / description
      Previous value: -"The token from this tool's preview, passed back verbatim to apply it. Single-use and bound to the previewed arguments."New value: +"The token from this tool's preview; pass it back to apply."
    • changedInput schema / properties / dry_run / description
      Previous value: -"Preview without a confirm token, for \"what would happen if\" questions; not the first step of a real change."New value: +"Preview only, no token issued: for \"what if\" questions, not the first step of a change."
    • changedInput schema / properties / service / enum
      Previous value: -[
      -  "radarr",
      -  "sonarr",
      -  "whisparr"
      -]New value: +[
      +  "radarr",
      +  "sonarr",
      +  "whisparr",
      +  "lidarr"
      +]
    • removedOutput schema / properties / audit_id
      Removed value: -{
      -  "type": "number"
      -}
    • removedOutput schema / properties / confirm_error
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / confirm_token
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / next_steps
      Removed value: -{
      -  "items": {
      -    "additionalProperties": {},
      -    "properties": {
      -      "arguments": {
      -        "additionalProperties": {},
      -        "properties": {},
      -        "type": "object"
      -      },
      -      "tool": {
      -        "type": "string"
      -      },
      -      "why": {
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "tool",
      -      "arguments",
      -      "why"
      -    ],
      -    "type": "object"
      -  },
      -  "type": "array"
      -}
    • removedOutput schema / properties / permission / properties / reason
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / permission / properties / remedy
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / result
      Removed value: -{}
    • removedOutput schema / properties / unchecked
      Removed value: -{
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
    • removedOutput schema / properties / warnings
      Removed value: -{
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
  2. Addedv1.84.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond destructiveHint=true, it discloses that the tool re-checks the finding before acting, that it refuses in Profilarr-synced instances, that the change is irreversible without a manual edit (the preview's old floor is the only record), and what the response contains. This is exactly the mutation context the annotations cannot convey.

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?

Front-loaded with the action, then constraints, then the confirm flow, with no filler; "nothing else" usefully caps the blast radius. The sentences are long and dense, which slightly hurts scanability, but every clause carries information.

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

Completeness5/5

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

For a destructive six-parameter mutation with an output schema, the description covers trigger, preconditions, refusals, irreversibility, the preview/confirm protocol, and return contents. Nothing an agent needs in order to call it safely is missing.

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 83%, so the baseline is 3; the description adds real meaning by tying `finding` to the `kind` value from get_profile_issues, `profile` to the printed name, `confirm` to the preview token, and distinguishing `dry_run` (what-if only) from the first step of an actual change.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (applies a fix) on a specific resource (quality profile's minimum custom format score) and narrows the trigger to two named finding kinds from get_profile_issues. An agent can distinguish it from get_profile_issues and from other fix_* tools without opening the schema.

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

Usage Guidelines5/5

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

Explicit about when to use (for unreachable_floor or knife_edge_floor findings from get_profile_issues) and when not to (stale findings are refused, Profilarr-synced instances are refused with a redirect to change it in Profilarr). Also defines the two-step flow: preview, then confirm.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.