Skip to main content
Glama
Augmented-Nature

SureChEMBL MCP Server

get_patent_family

Retrieve related patents and family connections for a specified patent ID from the SureChEMBL chemical patent database.

Instructions

Get patent family members and relationships for a patent

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
patent_idYesPatent ID to find family members for

Implementation Reference

  • The main handler function that validates the patent_id input and fetches patent family members from the SureChEMBL API endpoint `/document/{patent_id}/family/members`, returning the JSON response.
    private async handleGetPatentFamily(args: any) {
      if (!isValidIdArgs({ id: args.patent_id })) {
        throw new McpError(ErrorCode.InvalidParams, 'Invalid patent ID');
      }
    
      try {
        const response = await this.apiClient.get(`/document/${args.patent_id}/family/members`);
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(response.data, null, 2),
            },
          ],
        };
      } catch (error) {
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to get patent family: ${error instanceof Error ? error.message : 'Unknown error'}`
        );
      }
    }
  • src/index.ts:364-374 (registration)
    Tool registration definition in the ListToolsRequestSchema handler, including name, description, and input schema requiring 'patent_id'.
    {
      name: 'get_patent_family',
      description: 'Get patent family members and relationships for a patent',
      inputSchema: {
        type: 'object',
        properties: {
          patent_id: { type: 'string', description: 'Patent ID to find family members for' },
        },
        required: ['patent_id'],
      },
    },
  • src/index.ts:548-549 (registration)
    Dispatch case in the CallToolRequestSchema handler that routes to the handleGetPatentFamily method.
    case 'get_patent_family':
      return await this.handleGetPatentFamily(args);
  • Helper validation function used in the handler to validate the presence and format of the patent_id argument.
    const isValidIdArgs = (
      args: any
    ): args is { id: string } => {
      return (
        typeof args === 'object' &&
        args !== null &&
        typeof args.id === 'string' &&
        args.id.length > 0
      );
    };
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 states what the tool does but lacks details on permissions, rate limits, response format, or whether it's read-only or has side effects. This is a significant gap 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, clear sentence with no wasted words. It's front-loaded with the core purpose and efficiently conveys the tool's function without unnecessary elaboration.

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?

Given the tool's low complexity (1 parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks behavioral details and usage context, making it incomplete for effective agent use without additional inference.

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 schema description coverage is 100%, with the parameter 'patent_id' fully documented in the schema. The description doesn't add any extra meaning beyond the schema, such as format examples or constraints, so it meets the baseline for high schema coverage.

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 verb 'Get' and the resource 'patent family members and relationships for a patent', making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'search_patents' or 'get_patent_statistics', which prevents a perfect 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 prerequisites, exclusions, or compare to sibling tools such as 'search_by_patent_number' or 'get_patent_statistics', leaving usage context unclear.

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/SureChEMBL-MCP-Server'

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