Skip to main content
Glama

Trademark Dataset Statistics

trademark_stats

Retrieve trademark dataset statistics including total trademarks, status breakdown, top international classes, last updated timestamp, and data source information.

Instructions

Get statistics about the trademark dataset: total trademarks, status breakdown, top international classes, last updated timestamp, and data source information. Free endpoint.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration of the 'trademark_stats' tool on the MCP server via server.registerTool()
    server.registerTool(
      "trademark_stats",
      {
        title: "Trademark Dataset Statistics",
        description:
          "Get statistics about the trademark dataset: total trademarks, status breakdown, " +
          "top international classes, last updated timestamp, and data source information. Free endpoint.",
        inputSchema: {},
      },
      async () => {
        const res = await apiGet<TrademarkStatsResponse>("/api/v1/trademarks/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) },
          ],
        };
      },
    );
  • Handler function for trademark_stats — calls the /api/v1/trademarks/stats endpoint and returns the JSON response
    async () => {
      const res = await apiGet<TrademarkStatsResponse>("/api/v1/trademarks/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) },
        ],
      };
    },
  • TypeScript interface TrademarkStatsResponse defining the response shape (dataset, source, update_frequency, stats)
    interface TrademarkStatsResponse {
      dataset: string;
      source: string;
      update_frequency: string;
      stats: Record<string, unknown>;
    }
  • src/index.ts:17-28 (registration)
    Import of registerTrademarkTools from trademarks.ts module
    import { registerTrademarkTools } from "./tools/trademarks.js";
    import { registerPatentTools } from "./tools/patents.js";
    import { registerCompanyTools } from "./tools/company.js";
    import { registerCryptoTools } from "./tools/crypto.js";
    import { registerSanctionsTools } from "./tools/sanctions.js";
    import { registerWhaleTools } from "./tools/whales.js";
    import { registerLabelTools } from "./tools/labels.js";
    import { registerHolderTools } from "./tools/holders.js";
    import { registerDexTools } from "./tools/dex.js";
    import { registerContractTools } from "./tools/contracts.js";
    import { registerPmTools } from "./tools/pm.js";
    import { registerPmArbTools } from "./tools/pm_arb.js";
  • src/index.ts:44-44 (registration)
    Invocation of registerTrademarkTools to register all trademark tools including trademark_stats on the MCP server
    registerTrademarkTools(server);
Behavior2/5

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

No annotations are provided, so the description must cover behavioral traits. It states 'Get statistics' implying a read-only operation, but does not disclose potential rate limits, authentication requirements, data freshness, or caching behavior. For a zero-parameter endpoint, this is a minimal disclosure.

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: the first lists the data returned, the second identifies the endpoint as free. No wasted words, front-loaded with purpose.

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?

The description covers the main outputs but lacks details on how statistics are computed, any limitations (e.g., data update frequency), or error handling. Given no output schema, additional context would help agents understand robustness.

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?

The input schema has zero properties (100% schema description coverage), so the baseline is 4. The description does not add parameter information because there are none, which is appropriate.

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?

The description clearly states the verb 'Get' and the resource 'statistics about the trademark dataset', listing specific data items (total trademarks, status breakdown, etc.). It distinguishes from sibling tools like 'lookup_trademark' which is for individual queries, and 'query_trademarks' which likely returns full records.

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 aggregated stats but does not explicitly mention when to use this tool versus alternatives like 'lookup_trademark' or 'query_trademarks'. The 'Free endpoint' note is a minor guideline but lacks when-not-to-use or context-specific guidance.

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/carrierone/verilexdata-mcp'

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