Docs: Point attachment_refs at the pre-signed upload path - #496
Merged
Conversation
The attachment_refs description named create_file as the only source of a reference, so a client reading the parameter schema on create_task, update_task, create_comment or create_message had no reason to treat a create_upload_url reference as valid there. It now names create_upload_url first, which is the path that keeps file bytes out of the conversation. Drop the "tf_1a2b" example, which no issued reference resembles, in favour of the shape itself where the reference is an input, and remove the instruction to add Content-Length by hand: the handler already sets it in the headers it returns, so the description now agrees with the usage string and tells the caller to send exactly what came back. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The generated page embeds each tool's first sentence, which the create_upload_url wording change moved. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
rafaeljusto
approved these changes
Aug 26, 2026
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
2 participants
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.
What
attachment_refsoncreate_task,update_task,create_commentandcreate_messagedescribed its references as coming fromtwprojects-create_filealone. A client reading only the parameter schema — the common case — had no indication that atwprojects-create_upload_urlreference belonged there, which steers it onto the inline base64 path for files that already exist. The description now namescreate_upload_urlfirst.Two smaller corrections in the same file:
"tf_1a2b"is not the shape of an issued reference. Where the reference is an input (attachment_refs,add_project_file.reference) the description now gives the real shape; where it is an output (create_file,create_upload_url) the example is dropped, since the value is in the result.create_upload_urltold the caller to send the returned headers "adding Content-Length set to size", but the handler already setsContent-Lengthin the map it returns. It now says to send exactly the headers returned, which is what theusagestring already said.Verification
Tool descriptions only — no behaviour change.
go build ./...,go vetandgo test ./internal/twprojects/pass; no test asserted on the description text. All four descriptions were rendered to confirm the substitutions read correctly.🤖 Generated with Claude Code