Skip to main content
Glama
serper-search-mcp-server

serper-search-mcp-server

search_patents

Search Google Patents by query and country to retrieve publication numbers, assignees, inventors, and dates for patent and prior-art research.

Instructions

Google Patents search via Serper API. Returns patents with publication number, assignee, inventor, and dates. Always rich.

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

Input Schema

NameRequiredDescriptionDefault
queryYesPatent search query (max 400 chars / 50 words).
countryNoISO 3166-1 alpha-2 country code (e.g. "US", "GB"). Default: "US".
ui_langNoUI language (e.g. "en-US"). Default: "en".
providerNoSearch backend: auto (failover chain), serper, tavily, brave, exa, firecrawl. Default: auto.auto
max_charsNoTruncate response to this many characters (0 = no limit).
verbosityNoOutput density: auto (server picks per audience), compact (~800 tokens, dev fast path), standard (KG+Box+10), full (everything, always for places/shopping/images/scholar). Default: auto.auto
num_resultsNoResults (1–20, default 10). Note: >10 results uses 2 Serper credits.
search_langNoLanguage code (e.g. "en", "de"). Default: "en".
snippets_onlyNoReturn 1-line snippets only (token-saving for agents). Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It does contribute real value by naming the return fields and the upstream API, but it never states that the operation is read-only, how the provider failover chain behaves, or anything about Serper credit consumption and rate limits (the credit note only appears in the schema). "Always rich" is an assertion without operational meaning.

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?

Three short sentences, front-loaded with the resource and API, followed by the return shape. The only dead weight is the trailing "Always rich", which conveys no concrete information and could be cut or replaced with real behavioral detail.

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 nine-parameter search tool with no output schema, listing the returned fields is a meaningful compensation and the schema covers the rest. However, with no annotations at all, the description should say more about safety profile, cost (two Serper credits above ten results), and provider fallback behavior than it does.

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 all nine parameters — including provider, verbosity, snippets_only, max_chars, and the credit warning on num_results — are already documented in the schema. The description adds no additional semantics about parameter interaction or recommended settings, so the baseline of 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?

The description names a specific verb and resource ("Google Patents search via Serper API") and enumerates the returned fields (publication number, assignee, inventor, dates), so the agent knows exactly what domain this covers versus siblings like search_web or search_scholar. It stops short of explicitly contrasting itself with any named alternative.

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?

Usage is only implied by the name and the "Google Patents" scope; there is no statement of when to prefer this over search_web, deep_research, or other search siblings, and no exclusions or prerequisites. An agent can infer it is the patent-specific search, but must make the routing decision itself.

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