rust.wiki

Make a Rust key bind command (auto-run, crafting, chat, gestures...)

make_key_bind

Read-onlyIdempotent

Make a Rust key bind command (auto-run, crafting, chat, gestures...). The bind maker page (https://rust.wiki/calculators/bind-maker). Returns the bind line to paste into the F1 console and writecfg to save it. Without preset: every preset with its fields and suggested key, the bind syntax and the key names.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "make_key_bind"
  }
}

Input Schema

Name	Required	Description
`a`	No	The preset's first field (item ID, message, gesture, FOV, or the custom command).
`b`	No	The preset's second field (craft amount, second FOV).
`key`	No	Key name, e.g. `x`, `f1`, `mouse3` (default: the preset's suggestion).
`preset`	No	What the key does: autorun, sprintjump, crouch, autoattack, light_ads, craft, chat, teamchat, gesture, fov, voice, hoverloot, combatlog, kill, disconnect, custom. Left out = list the presets.
`modifier`	No	Optional held key for a combo: leftshift, leftcontrol, leftalt.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 14, 2026

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavior: the exact return payload is a `bind` line plus a `writecfg` command to persist it in the F1 console. That tells the agent the tool only generates text and does not touch a live game session, and that there is a follow-up save step. It stops short of describing error behavior for malformed keys or modifiers.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The capability statement and the preset list are front-loaded, and the response contract follows immediately — no filler. The mid-sentence line breaks and the bare URL insertion make it slightly less scannable than it could be, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the return-value burden itself and does so concretely (`bind` line plus `writecfg`). Combined with the 100%-covered input schema and the explicit no-preset discovery mode, an agent has everything needed to call this correctly on the first try.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so each parameter is already documented, including the `key` default and the "left out = list the presets" behavior for `preset`. The description adds only the framing that the preset's fields and suggested key are returned together, which is marginal over the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource ("Make a Rust key bind command") and immediately enumerates the kinds of binds (auto-run, crafting, chat, gestures), so an agent knows exactly what output it produces. It also points to the authoritative reference page, which disambiguates the tool from the numeric calculator siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly describes the two operating modes: with `preset` you get a concrete bind, and without `preset` you get a full preset catalog with fields and suggested keys — an explicit discovery path an agent can plan around. What's missing is guidance on sequencing (e.g., "call once without preset first, then again with one") or any note on invalid preset/key handling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All rust.wiki tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?