new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

MCP · Building servers and clients · all subjects

tools: declaration & validation

7 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Tool name length requirement

Tool names SHOULD be between 1 and 64 characters in length (inclusive).

Tool names are case-sensitive

Tool names are case-sensitive, meaning 'getUser' and 'getuser' are different tool names.

Tool name allowed characters

Tool names may include uppercase and lowercase ASCII letters (A-Z, a-z), digits (0-9), underscore (_), dash (-), dot (.), and forward slash (/).

Tool name disallowed characters

Tool names SHOULD NOT contain spaces, commas, or other special characters beyond the allowed set.

Tool names SHOULD be unique within namespace

Tool names SHOULD be unique within their namespace.

Valid tool name examples

Valid tool names include: getUser, user-profile/update, DATA_EXPORT_v2, admin.tools.list.

Tool naming rationale for flexible characters

The allowed character set (a-z, A-Z, 0-9, _, -, ., /) supports hierarchical and namespaced tool names, allows human-readable and machine-generated names, and accommodates conventions used by major clients like VS Code and Claude. Spaces and commas are restricted to avoid parsing issues and ambiguity.

Give your agent this brain