Blossom Research

Read a patent family record

get_patent

Read-onlyIdempotent

Retrieve one patent family by slug: the register facts (lead publication, family members by office, dates, owners and inventors as published), the abstract, the first claim as published with the publication it comes from, the patent type, the compounds and indications, the Blossom papers and patents that the family cites, the patents that cite it, and Blossom's editorial analysis when there is one. Use after search_patents, or when the chat is anchored to a patent page. The first claim of an application can differ from the granted claims. computedStatus is not a register check, and an empty contested field does not mean that nobody challenged the patent. Do not state that a patent is in force, valid or infringed: Blossom has no register status for most families.

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": {
      "slug": "<slug>"
    },
    "name": "get_patent"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already cover read-only and idempotency, yet the description adds genuinely non-obvious semantics: computedStatus is not a register check, an empty contested field is not proof of no challenge, the application's first claim can differ from granted claims, and the agent must not assert in-force/valid/infringed status. That is exactly the kind of interpretation guardrail structured fields cannot carry.

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 verb and scope, then shifts cleanly to usage and caveats. The long enumeration of returned fields is somewhat redundant given an output schema exists, but it is dense rather than padded.

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?

For a single-parameter read tool with an output schema, the description covers routing and the main interpretive pitfalls. It omits not-found/error behavior and how to obtain a slug in the first place, which are the remaining gaps.

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 0% for the single required 'slug' parameter; the description only restates that lookup is 'by slug' and implies the value comes from search_patents. It never states format, source, or what a bad slug produces, so it only marginally compensates for the bare schema.

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?

Opens with a specific verb and resource ('Retrieve one patent family by slug') and enumerates the record's contents, which lets an agent separate it from search_patents, count_patents and aggregate_patents without reading any schema.

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 explicit entry conditions — 'Use after search_patents, or when the chat is anchored to a patent page' — with a named prerequisite sibling. It does not explicitly say when to prefer aggregate_patents or count_patents instead, so the exclusion side is only implied.

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

All Blossom Research tools Inspect

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

Need Help?