Skip to main content
Glama

Nexscope Ecommerce Data MCP

Patent PDF Download

nexscope_patent_pdf_download
Read-only

Returns source PDF links for up to 100 patents. A related family patent may be used only when explicitly requested.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nexscope_patent_pdf_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
patentIdNoComma-separated patent IDs, up to 100; takes precedence over patentNumber.
patentNumberNoComma-separated publication numbers, up to 100.
replaceByRelatedNoUse a related family patent if the requested PDF is unavailable: string 1 for yes, 0 for no.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that the output is source links (not the documents) and a 100-record ceiling, but says nothing about link expiry, access restrictions, or partial-failure behavior when a PDF is unavailable.

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?

Two short sentences with no filler, and the core capability is front-loaded. The second sentence is arguably a parameter caveat that could be attached more directly to the parameter, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-output-schema, no-required-param lookup tool this is close to adequate, but the agent is left without knowing the response shape (e.g., a link per patent, error entries for unavailable PDFs) or how many IDs realistically resolve. A brief note on return behavior would close the gap.

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%, so all three parameters are already documented with examples and the patentId-over-patentNumber precedence is stated in the schema. The description reinforces the replaceByRelated constraint (related family patents only on explicit request), which adds modest meaning beyond the schema, so baseline 3 applies.

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 ("Returns source PDF links") plus a scale limit (up to 100 patents), and clarifies the payload is links rather than the PDF files themselves. It does not distinguish itself from sibling patent-data tools, but the purpose is unambiguous.

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 second sentence gives a conditional rule for the related-family fallback ("may be used only when explicitly requested"), which is genuine usage guidance. However, there is no explicit when-to-use vs. alternatives guidance, e.g. versus sibling tools that return family data or fulltext images.

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