Skip to main content
Glama

Patchfirst

Search CVEs

search
Read-onlyIdempotent

Search every published CVE (all tiers) by CVE id (full or partial, e.g. "CVE-2024-3400", "2024-34"), vendor, product or title words (e.g. "fortinet fortios", "confluence", "sql injection"). Ranked by match quality, then priority.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, default 10.
queryYesCVE id, vendor, product or title words

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world behavior, so the bar is low. The description still adds genuine non-schema behavior: results are ranked by match quality first and then by priority, which tells the agent how to interpret ordering and whether to trust the top hits.

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?

A single sentence, front-loaded with the verb and scope, with the accepted query shapes and examples carrying real information. Nothing in it is redundant with the title or schema, and no filler is present.

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?

With only two parameters, full schema coverage and no output schema, the definition gives what an agent needs to call it correctly: scope, accepted query forms, and ordering semantics. It does not indicate what a result record contains or how a no-match response looks, which is a minor gap but not an obstacle.

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. The description goes beyond the schema's terse "CVE id, vendor, product or title words" by showing that partial CVE ids are accepted ("2024-34") and that compound vendor+product strings work ("fortinet fortios"), which is meaning the schema never states.

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?

States a specific verb and resource ("Search every published CVE"), scopes it to "all tiers", and enumerates the accepted query fields (CVE id, vendor, product, title words). An agent knows exactly what the tool retrieves; it does not, however, contrast itself with siblings such as get_vulnerability or search-like alternatives.

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?

The phrase "all tiers" and the free-text query forms imply this is the broad discovery entry point, and ranking is explained. But there is no explicit when-to-use versus when-not, and no pointer to a more precise sibling when a single known CVE is wanted.

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