Skip to main content
Glama
Sign In

Nexscope

by io.github.nexscope
OverviewDiscussionsAdmin

Google Research Tools: search API

nexscope_data_patents_search
Read-only

Google Research Tools: search API.

Input Schema

NameRequiredDescriptionDefault
qYesGoogle Patents search query supports official advanced query syntax (such as `owner:"Company"`, `inventor:"Name"`, date operator). Maximum 1000 characters.
numNoNumber of results per page, range 10–100.
dupsNoDeduplication method; when not uploading, deduplication is based on patent family, `language` means deduplication is based on public text.
pageNoPage number, starting from 1.
sortNoSorting method: `new` (latest) or `old` (earliest); if not transmitted, sorted by relevance.
typeNoResult type: `PATENT` or `DESIGN`.
afterNoMinimum date, the format is the same as `before`.
beforeNoMaximum date, format `priority\|filing\|publication:YYYYMMDD`.
statusNoPatent status: `GRANT` or `APPLICATION`.
countryNoCountry code, multiple values separated by commas, for example `US,CN,WO`.
patentsNoWhether to include patent results.
scholarNoWhether to include Google Scholar results.
assigneeNoAssignee, multiple values separated by commas.
inventorNoInventor, multiple values are separated by commas.
languageNoLanguage, multiple values separated by English commas, use Google Patents official language value.
clusteredNoWhether to aggregate by category; upstream currently only supports `true`.
litigationNoLitigation Status: `YES` or `NO`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.7/5.0
Behavior1/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so safety is covered. The description adds nothing beyond that — no mention that this queries live Google Patents, how Scholar results are mixed in, or any rate/scope caveats.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Technically terse, but this is under-specification rather than conciseness: a single redundant sentence that duplicates the title and carries no actionable information.

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

Completeness1/5

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

A 17-parameter search tool with no output schema and no description content is severely under-documented. An agent gets no sense of what a result contains, how pagination interacts with num/page, or how duplication and clustering behave.

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%, so every one of the 17 parameters is documented in the schema itself. The description contributes no additional parameter guidance, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a restatement of the title ("Google Research Tools: search API") and never says what is being searched. Only the tool name hints at patents, and the description alone would not distinguish this from any other search sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No indication of when to use this tool versus alternatives such as nexscope_google_patent_search, nexscope_patent_search, nexscope_zhihuiya_* patent tools, or nexscope_data_ai_search_google_search. No exclusions, prerequisites, or context.

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

All Nexscope toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources