Skip to main content
Glama
Sign In

rust.wiki

by wiki.rust
OverviewDiscussionsAdmin

Search the RustProfit blog's Rust guides

search_guides
Read-onlyIdempotent

Search the RustProfit blog's Rust guides. Published guides from blog.rustprofit.com (monuments, recyclers, farming, base building, raiding, gear, NPCs, wipes, update explainers), best match first: every word must appear somewhere in the guide, and title matches rank above summary and tag matches, which rank above body-text matches. Link the url when citing one. Rust how-to guides from blog.rustprofit.com; cite and link the url.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "search_guides"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesWords to find in guide titles, summaries, tags and text.
limitNoMost results to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile needs no restating. The description adds real behavioral detail beyond them: strict AND matching across all query words and a three-tier relevance order (title > summary/tag > body), which tells the agent how results will be ordered and why a narrow query may return nothing.

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

Conciseness3/5

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

The ranking rules are front-loaded and useful, but the final sentence ('Rust how-to guides from blog.rustprofit.com; cite and link the url') restates the opening line and repeats the cite-the-url instruction already given mid-paragraph, so roughly a third of the text is redundant.

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

Completeness4/5

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

For a two-parameter search with no output schema, the description supplies the essentials: what corpus is searched, how matching and ranking work, and that results carry a `url` field to cite. Only the response shape beyond `url` (e.g. whether summaries/tags are returned) is left implicit.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, and the description exceeds it by specifying the matching semantics of `q` ('every word must appear somewhere in the guide') and the ranking dimensions searched (titles, summaries, tags, text), which the schema's one-line description does not convey. `limit` is left to the schema, which documents it adequately.

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

Purpose4/5

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

Specific verb+resource ('Search the RustProfit blog's Rust guides') with an enumerated topic scope (monuments, recyclers, raiding, wipes, etc.) that clearly separates it from siblings like search_items, search_servers, and search_workshop. It never names an alternative sibling, but the resource and domain make the distinction obvious.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer this is the tool for finding blog how-to content, and it prescribes citing the returned url. There is no explicit when-to-use/when-not or comparison against any sibling tool.

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

All rust.wiki toolsInspect
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