Skip to main content
Glama
Sign In
USPTO Patent MCP Server

USPTO Patent MCP Server

by riemannzeta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_status_code

Read-onlyIdempotent

Look up the meaning of a USPTO application status code and identify the examination stage it represents.

Instructions

Look up USPTO application status code meaning.

USE THIS TOOL WHEN: You encounter a status code in application data
and need to understand what examination stage it represents.

Args:
    code: Status code number (e.g., "30" for "Docketed New Case")

Returns:
    Status code description and examination stage.

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": {
      "code": "<code>"
    },
    "name": "get_status_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes

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": "get_status_codeOutput",
-  "type": "object"
-}New value: +null
  2. First observedv1.1.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the return shape (description plus examination stage), which is valuable since there is no output schema. It does not say how it behaves for an invalid code, a minor gap.

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 tightly scoped USE WHEN, Args, and Returns sections. Every sentence earns its place; the structured formatting is slightly heavier than needed for a single-parameter lookup.

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 trivial one-parameter lookup with no output schema, the description covers purpose, trigger, parameter semantics, and return values. Only the behavior on an unrecognized code is left unspecified.

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?

Schema description coverage is 0%, so the description must carry the parameter burden, and it does: it names the parameter, explains it is a status code number, and gives a concrete example ('30' for 'Docketed New Case'). It does not cover edge cases like unknown codes, keeping it short of a 5.

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 states a specific verb and resource: 'Look up USPTO application status code meaning.' The word 'application' distinguishes it from the sibling get_trademark_status_code, so an agent can route correctly, though no sibling is named explicitly.

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?

A distinct 'USE THIS TOOL WHEN' block gives an explicit triggering condition (encountering a status code in application data). It lacks a when-not clause or named alternative, but the trigger is unambiguous.

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