OpenAI API specs impose max 64 characters limit on tool names#619
OpenAI API specs impose max 64 characters limit on tool names#619antbob wants to merge 1 commit into
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request simplifies the names of two GitLab-related tools by replacing "merge_request" with "mr" in their identifiers: "get_failed_pipeline_jobs_from_merge_request" becomes "get_failed_pipeline_jobs_from_mr" and "get_authorized_comments_from_merge_request" becomes "get_authorized_comments_from_mr". The preliminary testing agent configuration is updated accordingly to use the new tool name. There are no review comments, and I have no feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
|
hearing that agents as skill will be possibly going away / obsolete soon, this might be irrelevant then so feel free to close. |
1 participant
This is something i ran into testing agents as skills with Claude Code using open weight models served by vLLM via OpenAI compatible API adapter. The problem is that OpenAI API spec limits tool names to 64 characters (which is a departure from the MCP spec where its up to 128 but its really up to implementation) and Claude Code prefixes everything so tool names blow up past 64 characters eg
mcp__ymir-privileged__get_failed_pipeline_jobs_from_merge_request
Since there is nothing that can be done about Claude Code behavior here its therefore a good workaround to shorten tool names where we can and where it doesnt compromise the meaning of those names so this PR does just that.