Verilex Data

Patent Dataset Statistics

patent_stats

Get patent dataset statistics: total count, type breakdown, top CPC sections, top assignees, last update time, and data source information.

Instructions

Get statistics about the patent dataset: total patents, type breakdown, top CPC sections, top assignees, last updated timestamp, and data source information. Free endpoint.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "patent_stats"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Implementation Reference

src/tools/patents.ts:153-185 (handler)

The handler for the 'patent_stats' tool. It registers the tool with MCP, takes no input parameters, calls the API endpoint /api/v1/patents/stats, and returns the statistics as JSON.

// ── Dataset stats ───────────────────────────────────────────────────────

server.registerTool(
  "patent_stats",
  {
    title: "Patent Dataset Statistics",
    description:
      "Get statistics about the patent dataset: total patents, type breakdown, " +
      "top CPC sections, top assignees, last updated timestamp, and data source information. Free endpoint.",
    inputSchema: {},
  },
  async () => {
    const res = await apiGet<PatentStatsResponse>("/api/v1/patents/stats");

    if (!res.ok) {
      return {
        content: [
          {
            type: "text" as const,
            text: `API error (${res.status}): ${JSON.stringify(res.data)}`,
          },
        ],
        isError: true,
      };
    }

    return {
      content: [
        { type: "text" as const, text: JSON.stringify(res.data, null, 2) },
      ],
    };
  },
);

src/tools/patents.ts:21-26 (schema)
TypeScript interface PatentStatsResponse defining the shape of the API response (dataset, source, update_frequency, stats).
```
interface PatentStatsResponse {
  dataset: string;
  source: string;
  update_frequency: string;
  stats: Record<string, unknown>;
}
```

src/tools/patents.ts:155-163 (registration)

Registration of the 'patent_stats' tool via server.registerTool with title, description, and empty inputSchema.

server.registerTool(
  "patent_stats",
  {
    title: "Patent Dataset Statistics",
    description:
      "Get statistics about the patent dataset: total patents, type breakdown, " +
      "top CPC sections, top assignees, last updated timestamp, and data source information. Free endpoint.",
    inputSchema: {},
  },

src/tools/patents.ts:6-6 (helper)
Comment line documenting the patent_stats tool purpose at the top of the file.
```
//   patent_stats      — Get patent dataset statistics
```

Schema Changelog

Changes observed during successful MCP inspections.

AddedMay 6, 2026
RemovedMar 18, 2026
First observedv0.3.1Mar 18, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, description bears full burden. It reveals it's a free endpoint but omits other behavioral traits (e.g., read-only, idempotency, rate limits). Adequate but not rich.

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

Conciseness5/5

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

Two concise sentences, front-loaded with action and enumerating outputs, with zero wasted words.

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?

Lists all return components explicitly, compensating for lack of output schema. Could add format or ordering details, but sufficient for an agent.

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?

Input schema has 0 parameters with 100% coverage, so baseline 3 is appropriate; description adds no parameter information as none exist.

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?

Description explicitly states the tool gets patent dataset statistics and lists specific outputs (total patents, type breakdown, etc.), clearly differentiating from sibling tools focused on other data domains.

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?

Mentions 'Free endpoint' as a usage consideration, and the sibling tools list indicates this is for patent stats vs. individual patent lookup or other dataset stats, though no explicit when-not-to-use is given.

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

Deploy Server