Skip to main content
Glama
riemannzeta

USPTO Patent MCP Server

by riemannzeta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

odp_get_continuity

Read-onlyIdempotent

Retrieve patent family continuity data to map parent applications, continuations, divisionals, and CIPs for a given application number.

Instructions

Get patent family/continuity data (parent and child applications).

USE THIS TOOL WHEN: You need to understand the patent family tree -
parent applications, continuations, divisionals, and CIPs.

Args:
    app_num: Application number without slashes (e.g., "14412875")

Returns:
    Continuity data showing parent/child relationships and priority claims.

Input Schema

NameRequiredDescriptionDefault
app_numYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.8.1
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "additionalProperties": true,
-      "title": "Result",
-      "type": "object"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "odp_get_continuityOutput",
-  "type": "object"
-}New value: +null
  2. First observedv1.1.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds only a brief statement of what the return contains (parent/child relationships, priority claims); it says nothing about auth, rate limits, or empty-result behavior.

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 one-line purpose followed by terse labeled sections (WHEN/Args/Returns). No filler, though the template headers add slight verbosity relative to the tiny payload.

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 no output schema, the description covers purpose, trigger, argument format, and return content. It is adequately complete; only edge-case behavior (no family found, invalid app number) is unaddressed.

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

Parameters4/5

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

With one parameter and 0% schema description coverage, the description carries the burden and does compensate: it specifies the format ('without slashes') and gives a concrete example ('14412875'), which an agent needs to form a valid call. It doesn't note validation or error behavior.

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 first line states a specific verb and resource ('Get patent family/continuity data') and clarifies the scope with 'parent and child applications'. It is distinguishable from siblings like odp_get_foreign_priority, though it never names an alternative to sharpen the boundary.

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?

The 'USE THIS TOOL WHEN' block gives clear context (understanding the family tree – parents, continuations, divisionals, CIPs), which is genuinely helpful selection guidance. It stops short of exclusions or naming a sibling tool to use instead.

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

Deploy Server

Other Tools