Crates

Get Crate

get_crate

Read-onlyIdempotent

Get full metadata for a specific crate (e.g., 'serde'). Returns description, downloads, latest version, repo, homepage, and categories.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	Exact crate name (e.g., "serde", "tokio")

Output Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Crate name
`homepage`	Yes	Homepage URL
`keywords`	Yes	List of keyword tags
`downloads`	Yes	Total download count
`categories`	Yes	List of category tags
`created_at`	Yes	Creation timestamp
`repository`	Yes	Repository URL
`updated_at`	Yes	Last update timestamp
`description`	Yes	Crate description
`documentation`	Yes	Documentation URL
`newest_version`	Yes	Latest published version
`recent_downloads`	Yes	Recent download count
`max_stable_version`	Yes	Latest stable version

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "categories": {
+      "description": "List of category tags",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "created_at": {
+      "description": "Creation timestamp",
+      "type": "string"
+    },
+    "description": {
+      "description": "Crate description",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "documentation": {
+      "description": "Documentation URL",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "downloads": {
+      "description": "Total download count",
+      "type": "number"
+    },
+    "homepage": {
+      "description": "Homepage URL",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "keywords": {
+      "description": "List of keyword tags",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "max_stable_version": {
+      "description": "Latest stable version",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "name": {
+      "description": "Crate name",
+      "type": "string"
+    },
+    "newest_version": {
+      "description": "Latest published version",
+      "type": "string"
+    },
+    "recent_downloads": {
+      "description": "Recent download count",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "repository": {
+      "description": "Repository URL",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "updated_at": {
+      "description": "Last update timestamp",
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "description",
+    "downloads",
+    "recent_downloads",
+    "newest_version",
+    "max_stable_version",
+    "repository",
+    "homepage",
+    "documentation",
+    "categories",
+    "keywords",
+    "created_at",
+    "updated_at"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "name": "serde"
+  },
+  {
+    "name": "tokio"
+  }
+]

First observedApr 22, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering safety and idempotency. The description adds value by detailing the returned metadata (description, downloads, etc.), which is beyond what annotations provide.

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 sentence that front-loads the purpose and output. Every word contributes meaning, with no waste.

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?

Given the tool has an output schema, the description does not need to explain return values. It fully covers the purpose, input, and output for a simple metadata retrieval tool.

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 coverage is 100% with a clear description of the 'name' parameter. The description repeats the example but does not add new constraints or formatting details, so it meets the baseline of 3.

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 verb 'Get', the resource 'full metadata for a specific crate', and lists the specific fields returned. It effectively distinguishes from sibling tools like search_crates (search) and get_crate_dependencies (dependencies).

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?

The description implies usage by providing an example ('e.g., serde') and stating it's for a specific crate, but it does not explicitly exclude other tools or provide when-not-to-use guidance. The context is clear enough for an agent to infer appropriate usage.

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

All Crates tools Inspect

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.