Skip to main content
Glama

Crates

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search Crates

search_crates
Read-onlyIdempotent

Search crates.io for Rust packages by keyword. Returns crate name, description, downloads, latest version, and repo URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results to return (default 10, max 100)
queryYesSearch query string

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYesTotal number of matching crates
cratesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "crates": {
+      "items": {
+        "properties": {
+          "description": {
+            "description": "Short description of the crate",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "downloads": {
+            "description": "Total download count",
+            "type": "number"
+          },
+          "homepage": {
+            "description": "Homepage URL",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "max_stable_version": {
+            "description": "Latest stable version",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Crate name",
+            "type": "string"
+          },
+          "newest_version": {
+            "description": "Latest published version",
+            "type": "string"
+          },
+          "repository": {
+            "description": "Repository URL",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "updated_at": {
+            "description": "Last update timestamp",
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "description",
+          "downloads",
+          "newest_version",
+          "max_stable_version",
+          "repository",
+          "homepage",
+          "updated_at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Total number of matching crates",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "crates"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "web framework"
+  },
+  {
+    "limit": 20,
+    "query": "async runtime"
+  }
+]
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering safety and idempotency. The description adds information about returned fields but does not elaborate on behavioral traits beyond annotations.

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

Conciseness5/5

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

The description is a single concise sentence that immediately states the purpose and key return values. Every word is useful, and there is no unnecessary verbosity.

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?

The tool is simple (search), and the description covers main functionality. An output schema exists. The description mentions return fields, though missing details like sorting or pagination. Still, it is largely complete for the tool's complexity.

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 the input schema already fully documents parameters. The description does not add any additional parameter semantics beyond what is in the schema.

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 clearly states the tool searches crates.io for Rust packages by keyword, listing specific return fields (name, description, downloads, version, repo URL). This distinguishes it from sibling tools, which are unrelated to crate searching.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus alternatives, nor does it mention when not to use it. Sibling tools are diverse, but no explicit usage context is provided.

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

All Crates toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources