Skip to main content
Glama
flyanima

Open Search MCP

by flyanima

ieee_standards_search

Search IEEE standards and specifications by query, type, or committee to find technical requirements for projects and research.

Instructions

Search IEEE standards and specifications

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query for IEEE standards (e.g., "wireless communication", "software engineering", "cybersecurity")
standardTypeNoStandard type: all, active, inactive, draft, withdrawnactive
committeeNoIEEE committee (e.g., "802", "1394", "1588")
maxResultsNoMaximum number of standards to return (1-100)

Implementation Reference

  • The execute handler function implementing the ieee_standards_search tool. It destructures input args, generates mock IEEE standards data based on query, standardType, committee, and maxResults, and returns structured results or error.
    execute: async (args: any) => {
      const { query, standardType = 'active', committee = '', maxResults = 10 } = args;
    
      try {
        // 模拟IEEE标准搜索结果
        const mockStandards = Array.from({ length: Math.min(maxResults, 10) }, (_, i) => {
          const committees = ['802', '1394', '1588', '754', '1003', '1076', '1149', '1275', '1364', '1471'];
          const selectedCommittee = committee || committees[Math.floor(Math.random() * committees.length)];
          
          return {
            standardId: `IEEE ${selectedCommittee}.${i + 1}`,
            title: `IEEE Standard for ${query} - Part ${i + 1}`,
            description: `This standard defines the requirements and specifications for ${query} systems and implementations. It provides guidelines for design, testing, and deployment of ${query} technologies in various applications.`,
            status: standardType === 'all' ? ['Active', 'Inactive', 'Draft', 'Withdrawn'][Math.floor(Math.random() * 4)] : standardType.charAt(0).toUpperCase() + standardType.slice(1),
            committee: selectedCommittee,
            workingGroup: `${selectedCommittee}.${Math.floor(Math.random() * 20) + 1}`,
            approvalDate: new Date(Date.now() - Math.random() * 365 * 10 * 24 * 60 * 60 * 1000).toISOString().split('T')[0],
            lastRevision: new Date(Date.now() - Math.random() * 365 * 5 * 24 * 60 * 60 * 1000).toISOString().split('T')[0],
            pages: Math.floor(Math.random() * 200) + 50,
            scope: `This standard covers the technical specifications and requirements for ${query} implementations.`,
            purpose: `To establish uniform requirements for ${query} systems and ensure interoperability.`,
            keywords: [
              query.toLowerCase(),
              'IEEE standard',
              'technical specification',
              'engineering standard'
            ],
            relatedStandards: [
              `IEEE ${selectedCommittee}.${i}`,
              `IEEE ${selectedCommittee}.${i + 2}`,
              `ISO/IEC ${Math.floor(Math.random() * 30000) + 10000}`
            ],
            url: `https://standards.ieee.org/standard/${selectedCommittee}_${i + 1}.html`,
            purchaseUrl: `https://standards.ieee.org/findstds/standard/${selectedCommittee}.${i + 1}.html`,
            price: `$${Math.floor(Math.random() * 200) + 50}`,
            format: ['PDF', 'Print'],
            language: 'English'
          };
        });
    
        return {
          success: true,
          data: {
            source: 'IEEE Standards',
            query,
            standardType,
            committee,
            totalResults: mockStandards.length,
            standards: mockStandards,
            timestamp: Date.now(),
            searchMetadata: {
              database: 'IEEE Standards Database',
              searchCriteria: {
                query,
                standardType: standardType !== 'all' ? standardType : 'any',
                committee: committee || 'any'
              }
            }
          }
        };
      } catch (error) {
        return {
          success: false,
          error: error instanceof Error ? error.message : 'Failed to search IEEE standards'
        };
      }
    }
  • Input schema defining parameters for ieee_standards_search: query (required string), standardType (enum), committee (string), maxResults (number 1-100).
    inputSchema: {
      type: 'object',
      properties: {
        query: {
          type: 'string',
          description: 'Search query for IEEE standards (e.g., "wireless communication", "software engineering", "cybersecurity")'
        },
        standardType: {
          type: 'string',
          description: 'Standard type: all, active, inactive, draft, withdrawn',
          default: 'active',
          enum: ['all', 'active', 'inactive', 'draft', 'withdrawn']
        },
        committee: {
          type: 'string',
          description: 'IEEE committee (e.g., "802", "1394", "1588")'
        },
        maxResults: {
          type: 'number',
          description: 'Maximum number of standards to return (1-100)',
          default: 10,
          minimum: 1,
          maximum: 100
        }
      },
      required: ['query']
    },
  • Registration of the ieee_standards_search tool using registry.registerTool, including name, description, category, source, inputSchema, and execute handler.
      name: 'ieee_standards_search',
      description: 'Search IEEE standards and specifications',
      category: 'academic',
      source: 'IEEE',
      inputSchema: {
        type: 'object',
        properties: {
          query: {
            type: 'string',
            description: 'Search query for IEEE standards (e.g., "wireless communication", "software engineering", "cybersecurity")'
          },
          standardType: {
            type: 'string',
            description: 'Standard type: all, active, inactive, draft, withdrawn',
            default: 'active',
            enum: ['all', 'active', 'inactive', 'draft', 'withdrawn']
          },
          committee: {
            type: 'string',
            description: 'IEEE committee (e.g., "802", "1394", "1588")'
          },
          maxResults: {
            type: 'number',
            description: 'Maximum number of standards to return (1-100)',
            default: 10,
            minimum: 1,
            maximum: 100
          }
        },
        required: ['query']
      },
      execute: async (args: any) => {
        const { query, standardType = 'active', committee = '', maxResults = 10 } = args;
    
        try {
          // 模拟IEEE标准搜索结果
          const mockStandards = Array.from({ length: Math.min(maxResults, 10) }, (_, i) => {
            const committees = ['802', '1394', '1588', '754', '1003', '1076', '1149', '1275', '1364', '1471'];
            const selectedCommittee = committee || committees[Math.floor(Math.random() * committees.length)];
            
            return {
              standardId: `IEEE ${selectedCommittee}.${i + 1}`,
              title: `IEEE Standard for ${query} - Part ${i + 1}`,
              description: `This standard defines the requirements and specifications for ${query} systems and implementations. It provides guidelines for design, testing, and deployment of ${query} technologies in various applications.`,
              status: standardType === 'all' ? ['Active', 'Inactive', 'Draft', 'Withdrawn'][Math.floor(Math.random() * 4)] : standardType.charAt(0).toUpperCase() + standardType.slice(1),
              committee: selectedCommittee,
              workingGroup: `${selectedCommittee}.${Math.floor(Math.random() * 20) + 1}`,
              approvalDate: new Date(Date.now() - Math.random() * 365 * 10 * 24 * 60 * 60 * 1000).toISOString().split('T')[0],
              lastRevision: new Date(Date.now() - Math.random() * 365 * 5 * 24 * 60 * 60 * 1000).toISOString().split('T')[0],
              pages: Math.floor(Math.random() * 200) + 50,
              scope: `This standard covers the technical specifications and requirements for ${query} implementations.`,
              purpose: `To establish uniform requirements for ${query} systems and ensure interoperability.`,
              keywords: [
                query.toLowerCase(),
                'IEEE standard',
                'technical specification',
                'engineering standard'
              ],
              relatedStandards: [
                `IEEE ${selectedCommittee}.${i}`,
                `IEEE ${selectedCommittee}.${i + 2}`,
                `ISO/IEC ${Math.floor(Math.random() * 30000) + 10000}`
              ],
              url: `https://standards.ieee.org/standard/${selectedCommittee}_${i + 1}.html`,
              purchaseUrl: `https://standards.ieee.org/findstds/standard/${selectedCommittee}.${i + 1}.html`,
              price: `$${Math.floor(Math.random() * 200) + 50}`,
              format: ['PDF', 'Print'],
              language: 'English'
            };
          });
    
          return {
            success: true,
            data: {
              source: 'IEEE Standards',
              query,
              standardType,
              committee,
              totalResults: mockStandards.length,
              standards: mockStandards,
              timestamp: Date.now(),
              searchMetadata: {
                database: 'IEEE Standards Database',
                searchCriteria: {
                  query,
                  standardType: standardType !== 'all' ? standardType : 'any',
                  committee: committee || 'any'
                }
              }
            }
          };
        } catch (error) {
          return {
            success: false,
            error: error instanceof Error ? error.message : 'Failed to search IEEE standards'
          };
        }
      }
    });
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers minimal information. It doesn't mention whether this is a read-only operation, what authentication might be required, rate limits, pagination behavior, or what format results will be returned in. The description is too sparse for a search tool with multiple parameters.

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 extremely concise at just 5 words, front-loading the essential purpose without any wasted words. Every element earns its place, though this brevity comes at the cost of completeness in other dimensions.

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?

For a search tool with 4 parameters and no output schema, the description is insufficient. It doesn't explain what kind of results to expect, how they're structured, or provide any behavioral context. With no annotations and no output schema, the agent lacks crucial information about how to interpret and use the tool's results effectively.

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?

With 100% schema description coverage, the input schema already documents all 4 parameters thoroughly with descriptions, defaults, enums, and constraints. The description adds no additional parameter semantics beyond what's in the schema, so it meets the baseline expectation but doesn't provide extra value.

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 action ('Search') and target resource ('IEEE standards and specifications'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'search_ieee' or 'search_arxiv', which could cause confusion about scope boundaries.

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?

No guidance is provided about when to use this tool versus alternatives like 'search_ieee' or 'search_semantic_scholar'. The description offers no context about appropriate use cases, prerequisites, or limitations, leaving the agent to guess based on tool names alone.

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/flyanima/open-search-mcp'

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