Skip to main content
Glama

get_crate_info

Read-only: fetch public metadata for a Rust crate from the free, unauthenticated crates.io API (https://crates.io/api/v1/crates/). Returns name, latest version, description, license, repository, downloads, recent_downloads, max_version, updated_at, documentation and homepage. No login or API key.

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": {
      "name": "<name>"
    },
    "name": "get_crate_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesCrate name, e.g. serde (letters, digits, - and _ only, max 64 chars)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it declares read-only semantics, public/free/unauthenticated access, and the concrete upstream URL. It does not mention rate limiting or User-Agent requirements, which are real behavioral constraints of the crates.io API, so it stops short of a 5.

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?

Front-loaded with the safety profile ('Read-only') followed by source and return surface; two sentences, no filler. The return-field list is long but substitutes for a missing output schema, so it earns its place.

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?

For a single-parameter read tool with no output schema, the description supplies exactly what is otherwise missing: auth requirements, upstream source, and an explicit enumeration of returned fields. Nothing an agent needs before calling is absent.

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% — the crate name format (letters, digits, hyphen, underscore, max 64 chars) is already in the schema. The description adds no additional parameter meaning beyond naming the resource, so the baseline 3 applies.

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?

States a specific verb ('fetch') and resource ('public metadata for a Rust crate') plus the exact upstream endpoint, so the agent knows precisely what will be retrieved and from where. The enumerated return fields further pin down the resource.

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?

Explicitly frames the context of use: free, unauthenticated, no login or API key, so an agent knows it can call this without credentials or setup. There are no sibling tools to disambiguate against and no exclusions are stated, which keeps it below a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources