Skip to content

docs: clarify server-specific tool naming #4907

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
liang0417 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: clarify server-specific tool naming #4907

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,8 +65,12 @@ uv run ruff check .
- Zod schemas for tool input validation
- 2-space indentation, trailing commas in multi-line objects
- camelCase for variables/functions, PascalCase for types/classes, UPPER_CASE for constants
- kebab-case for file names and registered tools/prompts/resources
- Verb-first tool names (e.g., `get-file-info`, not `file-info`)
- kebab-case for file names; for registered tools, prompts, and resources, follow
the existing public convention of the server you are changing (for example,
snake_case in `filesystem` and `memory`, kebab-case in `everything`)
- Never rename a published tool, prompt, or resource only to change its casing
- Prefer verb-first tool names in the server's existing style (for example,
`get_file_info` in `filesystem` or `get-annotated-message` in `everything`)
- Imports grouped: external first, then internal

### Python
Expand Down
Loading