Skip to main content
Glama

get_uspto_patent_intelligence

Read-only

Use when assessing a company IP portfolio strength, tracking competitor patent activity, or preparing M&A patent due diligence. Returns USPTO filing rollups by assignee — patent counts, filing years, and CPC classification. Example: Qualcomm — 47,000+ active patents, 3,200 filed in 2023, concentrated in 5G and AI/ML — top 3 CPC codes represent 61% of portfolio — IP moat assessment critical for semiconductor M&A. Source: USPTO PatentsView synced data. $0.02 USDC per call.

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": {
      "assignee_name": "<assignee_name>"
    },
    "name": "get_uspto_patent_intelligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
patent_yearNo
assignee_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds real context beyond that — the upstream source (USPTO PatentsView synced data) and the $0.02 USDC per-call cost, which affects how an agent budgets calls. It does not mention freshness/lag, rate limits, or what happens for an unknown assignee, so this stays a 3.

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?

Front-loaded with the 'Use when' trigger, then what is returned, then an illustrative example, then source and price. Efficient overall, though the Qualcomm example is dense and mixes output illustration with interpretive commentary ('IP moat assessment critical for semiconductor M&A') that does not add call guidance.

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?

No output schema exists, and the description compensates well by enumerating the returned content (patent counts, filing years, CPC distribution) plus source and cost. The remaining gap is the undocumented optional patent_year parameter, which leaves an agent guessing whether it narrows the result set.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning and largely does not. 'By assignee' implies assignee_name is the entity key, but the optional patent_year filter is never identified as a filter — 'filing years' appears only as a returned field, which could mislead an agent into thinking it is output-only.

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

Purpose5/5

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

States a specific verb and resource: 'Returns USPTO filing rollups by assignee — patent counts, filing years, and CPC classification.' The USPTO/patent framing clearly separates it from the financial, docket, and contract siblings in the catalog.

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

Usage Guidelines4/5

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

Gives three concrete when-to-use scenarios: IP portfolio strength assessment, competitor patent activity tracking, and M&A patent due diligence. It stops short of naming an alternative tool or stating when not to use it, but the triggering contexts are unambiguous.

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