Skip to main content
Glama

patentpulse

Search global patents, analyze freedom-to-operate, assess prior art, and monitor competitor landscapes across major patent offices worldwide.

Instructions

PatentPulse: PatentPulse — global IP intelligence: USPTO/EPO/WIPO/JPO/CNIPA patent search, FTO analysis, SEP licensing, trademark clearance, prior art, and competitor patent landscape. Multilingual.

Coverage: Global

Endpoints: • global ($0.10): Jurisdiction-specific patent search — EPO, CNIPA, KIPO, JPO, WIPO PCT, DPMA, UKIPO, CIPO, IP Australia, INPI • search ($0.10): Global patent search (USPTO + global synthesis) • cliff ($0.10): Pharma patent cliff analysis • fto ($0.10): Freedom-to-operate analysis • assignee ($0.10): Company patent portfolio intelligence • prior-art ($0.10): Prior art search • status ($0.10): Patent status lookup • trends ($0.10): Patent filing trends • sep ($0.10): Standard Essential Patent landscape • competitor ($0.10): Competitor R&D intelligence • trademark ($0.10): Trademark clearance search

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesWhich endpoint to call. Options: global | search | cliff | fto | assignee | prior-art | status | trends | sep | competitor | trademark
langNolang
qNoSearch query — technology keyword or assignee/company name
jurisdictionNoPatent office code. EP = EPO (Europe), WO = WIPO PCT (international), CN = CNIPA (China), KR = KIPO (Korea), JP = JPO (Japan), DE = DPMA (Ge
typeNotype
drugNoDrug name — generic or brand (e.g. humira, ozempic, keytruda)
technologyNoTechnology or product description for FTO analysis
countryNoTarget jurisdiction (e.g. US, EU, China, Japan, global)
companyNoCompany or institution name (e.g. Qualcomm, MIT, Samsung)
inventionNoInvention description — be specific about the novel aspects
idNoPatent number (e.g. 10000000 or US10,000,000)
areaNoTechnology area (e.g. CRISPR, solid-state battery, large language models)
cpcNoCPC classification code (e.g. G06N, H01M)
standardNoTechnology standard
markNoTrademark to search (e.g. PulsePay, NeuralFlow)
goodsNoGoods or services description (e.g. payment software, clothing, restaurant services)
Behavior2/5

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

With no annotations, the description carries full burden. It mentions multilingual and pricing per endpoint but does not disclose rate limits, authentication, data freshness, or other behavioral traits. More context is needed for safe invocation.

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

Conciseness3/5

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

The description is front-loaded with 'PatentPulse: global IP intelligence' but then becomes a lengthy list of endpoints. It is somewhat verbose and could be more concise without losing clarity. The structure as a list is clear.

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?

Given the tool's complexity (16 parameters, many endpoints), the description covers each endpoint's purpose. However, it lacks information on output format or parameter combinations. No output schema, so more detail would help.

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 baseline is 3. The description adds minimal value beyond the schema, only listing endpoint names and brief hints (e.g., 'Drug name — generic or brand'). No significant enrichment.

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 clearly states 'global IP intelligence' and lists specific use cases like patent search, FTO, SEP licensing, etc. It distinguishes from siblings by its patent focus. However, the verb/resource is somewhat implicit, as it lists endpoints rather than a single action.

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 description implies usage for patent-related tasks via endpoint names, but lacks explicit guidance on when to use this tool versus other pulse tools. No 'when not to use' or alternatives are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GTCC777/pulsenetwork-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server