fix: annotate throttler ratio with human-readable description#4
Open
fix: annotate throttler ratio with human-readable description#4
Conversation
The PlanetScale throttler ratio is a brake (0 = full speed, 100 = paused), which is counter-intuitive. An LLM misread `ratio: 0` as "fully paused" during a production deploy request audit. Adding `ratio_description` to the response ensures the semantics are visible at interpretation time, not just in the tool schema. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
lorcan
force-pushed
the
lorcan/deploy-request-throttler-semantics
branch
from
3502fe3 to
44041be
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why?
PlanetScale's throttler ratio uses brake semantics: 0 means "no braking" (full speed), 100 means "fully braked" (paused). This is counter-intuitive — a ratio of 0 looks like "zero work" or "fully paused" when read without context. An LLM consuming this tool's output misinterpreted
ratio: 0as "deployment is frozen" when it was actually running at maximum speed.How?
Adds a
ratio_descriptionfield alongside each numericratiovalue in the throttler configurations response, and updates the tool description to explain the brake model.Generated with Claude Code