Skip to main content
Glama

search_patents

Find chemical patents and intellectual property data by searching with PubChem Compound IDs or patent queries to access relevant chemical innovation information.

Instructions

Search for chemical patents and intellectual property information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cidNoPubChem Compound ID (CID)
queryNoPatent search query (alternative to CID)

Implementation Reference

  • The handler function for the 'search_patents' tool. It currently returns a placeholder response indicating that patent search is not yet implemented.
    private async handleSearchPatents(args: any) {
      return { content: [{ type: 'text', text: JSON.stringify({ message: 'Patent search not yet implemented', args }, null, 2) }] };
    }
  • Input schema definition for the 'search_patents' tool, specifying optional cid or query parameters.
    inputSchema: {
      type: 'object',
      properties: {
        cid: { type: ['number', 'string'], description: 'PubChem Compound ID (CID)' },
        query: { type: 'string', description: 'Patent search query (alternative to CID)' },
      },
      required: [],
    },
  • src/index.ts:696-707 (registration)
    Tool registration in the list of available tools, including name, description, and input schema.
    {
      name: 'search_patents',
      description: 'Search for chemical patents and intellectual property information',
      inputSchema: {
        type: 'object',
        properties: {
          cid: { type: ['number', 'string'], description: 'PubChem Compound ID (CID)' },
          query: { type: 'string', description: 'Patent search query (alternative to CID)' },
        },
        required: [],
      },
    },
  • src/index.ts:804-805 (registration)
    Dispatcher switch case that routes calls to the 'search_patents' handler function.
    case 'search_patents':
      return await this.handleSearchPatents(args);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the search function without detailing aspects like whether it's read-only, potential rate limits, authentication needs, output format, or pagination behavior. For a search tool with zero annotation coverage, this is a significant gap in transparency.

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?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, with every part contributing essential information, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a search tool with two parameters, no annotations, and no output schema, the description is incomplete. It lacks details on behavioral traits, usage guidelines, and output expectations, which are crucial for an agent to effectively invoke this tool. The description does not compensate for the missing structured data.

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?

The description mentions searching by 'chemical patents and intellectual property information', which loosely relates to the parameters (CID for compound-based search, query for text-based search). However, with 100% schema description coverage, the schema already documents both parameters thoroughly. The description adds minimal value beyond what's in the schema, meeting the baseline score of 3.

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 clearly states the tool's purpose as 'Search for chemical patents and intellectual property information', which includes a specific verb ('Search') and resource type ('chemical patents and intellectual property information'). It distinguishes itself from most sibling tools that focus on compound analysis, bioactivities, or other searches, though it doesn't explicitly differentiate from all search-related siblings like 'search_compounds' or 'search_by_target'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context for choosing between CID or query parameters, or how it differs from other search tools in the sibling list (e.g., 'search_compounds' or 'search_by_target'). This leaves the agent with minimal direction on appropriate usage scenarios.

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/k-lordbodin7/PubChem-MCP-Server'

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