Skip to main content
Glama

Rust Crate Security Advisories — buy per-query in-session (rustsecwatch)

by com.a2awire
OverviewAdmin

data_preview

Read-onlyIdempotent

✅ No API key needed — call this now. Listing: rustsecwatch: RustSec Crate Security Advisories. Price 0.01 USDC/query (max 20 queries/session). Sample questions: What are the newest RustSec advisories this week?; Which crates were removed from crates.io for malicious code?. FREE preview — no key, no payment. Try one of the sample questions now.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugNoPublic listing slug. Defaults to the routed session's listing when connected via /mcp/data/{slug}/http.
questionNoOptional free-text question you'd ask this data (echoed back).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Description adds 'public metadata only' and 'echoed back' for the question parameter, consistent with annotations (readOnly, idempotent). No contradictory or unexpected behavior disclosed.

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?

Contains marketing-style fluff ('✅ No API key needed — call this now') and extra pricing details that are not essential for core understanding. The structure is acceptable but includes redundant persuasive language.

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?

Given the simple preview nature, the description provides sufficient information: purpose, free access, public metadata, sample questions, and parameter details. No output schema, but not expected for this tool.

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 description coverage is 100% and both parameters (slug, question) are clearly described, with additional context in the overall description about sample questions and echo behavior.

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?

Clearly states a specific purpose: a free, guest-callable preview of a data listing, with explicit sample questions. Distinguishes itself from sibling tools by emphasizing it is a taste with no API key or payment.

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?

Implies usage for initial exploration before committing to paid queries via the 'No API key needed' and 'FREE preview' statements. Does not explicitly name alternatives but the preview nature is evident.

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

All Rust Crate Security Advisories — buy per-query in-session (rustsecwatch) toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources