Skip to main content
Glama

SBOM Dependency CVE & US CISA Known Exploited Vulnerability MCP

Search Global Patent & Scholarly Prior-Art Works

search_patent_academic_prior_art
Read-onlyIdempotent

Searches 250M+ technical works for patent novelty and prior-art assessment, returning reconstructed abstracts, DOIs, and citation counts.

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_patent_academic_prior_art"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesInvention concept or technical mechanism

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive, so the safety profile is covered. The description adds genuine context by disclosing the return payload (reconstructed abstracts, DOIs, citation counts) and the corpus scale, but says nothing about result caps, ranking, or pagination limits that an agent would need to plan around.

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?

A single front-loaded sentence that packs purpose, scale, and return contents with no filler. The '250M+' figure borders on marketing but does usefully signal recall expectations, so it earns its place.

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?

For a one-parameter, annotation-rich, output-schema-less search tool, the description covers what it does and what it returns, which is close to sufficient. The main omission is any note on result volume or ranking behavior, a minor gap given the tool's simplicity.

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% for the single 'query' parameter ('Invention concept or technical mechanism'), so the schema carries the burden. The description only restates the corpus being searched and adds no syntax, phrasing, or specificity guidance beyond what the schema already says.

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 ('Searches') and resource ('250M+ technical works') plus the domain purpose ('patent novelty and prior-art assessment'), which is clearly distinct from the CVE/SBOM/clinical-trial siblings. It stops short of explicitly naming or contrasting an alternative tool, so it lands just under a 5.

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 'for patent novelty and prior-art assessment' implies the intended use case, but there is no explicit when-to-use/when-not-to-use guidance and no routing to alternatives for adjacent needs such as clinical or vulnerability research. Usage is inferable rather than stated.

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.