Skip to main content
Glama
Augmented-Nature

Unofficial PubChem MCP Server

search_patents

Find chemical patents and intellectual property data using PubChem Compound IDs or search queries to identify patent coverage for compounds.

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 the 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) }] };
    }
  • The tool definition including name, description, and input schema for 'search_patents' registered in the ListTools response.
    {
      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)
    The switch case in the CallToolRequest handler that dispatches 'search_patents' calls to the handleSearchPatents method.
    case 'search_patents':
      return await this.handleSearchPatents(args);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states what the tool does (searching) without any details on behavioral traits like whether it's read-only, potential rate limits, authentication needs, or what the search results might include. This is inadequate for a tool with no annotation coverage.

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 any unnecessary words. It is appropriately sized and front-loaded, making it easy to understand at a glance.

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 and no output schema, the description is incomplete. It lacks details on behavioral aspects, usage guidelines, and what to expect in results, which are crucial for effective tool invocation in this context.

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 input schema has 100% description coverage, so the schema already documents both parameters (CID and query) adequately. The description adds no additional meaning beyond what the schema provides, such as explaining the relationship between CID and query or providing usage examples, resulting in the baseline score.

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 searching for chemical patents and intellectual property information, which is a specific verb+resource combination. However, it doesn't distinguish itself from potential sibling tools like 'search_compounds' or 'search_by_target' that might also search but for different types of information, so it doesn't reach the highest score.

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 any specific contexts, prerequisites, or exclusions, such as when to prefer CID-based searches over query-based ones or how it differs from other search tools in the sibling list like 'search_compounds'.

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/Augmented-Nature/Augmented-Nature-PubChem-MCP-Server'

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