Skip to main content
Glama

search_specifications

Search 3GPP telecommunications specifications to find implementation requirements, technical procedures, and structured metadata for AI agents and developers.

Instructions

Search 3GPP specifications using TSpec-LLM dataset and official metadata. Returns actual specification content and structured metadata for agent consumption.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query (e.g., "5G charging CHF implementation", "handover procedures", "authentication security")
max_resultsNoMaximum number of results to return (default: 5)
series_filterNoFilter by specification series (e.g., ["32", "33", "38"])
release_filterNoFilter by 3GPP release (e.g., ["Rel-16", "Rel-17"])
include_contentNoInclude detailed specification content from TSpec-LLM (default: true)
formatNoResponse format - agent_ready provides structured JSON optimized for AI agentsagent_ready

Implementation Reference

  • Core handler function that executes the search_specifications tool. Constructs an EnhancedSearchRequest from args, calls apiManager.enhancedSearch, formats results based on the specified format (agent_ready, summary, detailed), and handles errors.
    async execute(args: SearchSpecificationsArgs) {
      try {
        const request: EnhancedSearchRequest = {
          query: args.query,
          include_tspec_content: args.include_content !== false,
          include_official_metadata: true,
          max_results: args.max_results || 5,
          series_filter: args.series_filter,
          release_filter: args.release_filter
        };
    
        const searchResults = await this.apiManager.enhancedSearch(request);
    
        const format = args.format || 'agent_ready';
    
        switch (format) {
          case 'agent_ready':
            return {
              content: [
                {
                  type: 'text',
                  text: JSON.stringify(this.formatForAgent(searchResults), null, 2)
                }
              ]
            };
    
          case 'summary':
            return {
              content: [
                {
                  type: 'text',
                  text: this.formatSummary(searchResults)
                }
              ]
            };
    
          case 'detailed':
          default:
            return {
              content: [
                {
                  type: 'text',
                  text: this.formatDetailed(searchResults)
                }
              ]
            };
        }
    
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error searching specifications: ${error instanceof Error ? error.message : 'Unknown error'}`
            }
          ],
          isError: true
        };
      }
    }
  • Defines the tool schema including name 'search_specifications', description, and detailed inputSchema with properties for query, filters, and format options.
    getDefinition() {
      return {
        name: 'search_specifications',
        description: 'Search 3GPP specifications using TSpec-LLM dataset and official metadata. Returns actual specification content and structured metadata for agent consumption.',
        inputSchema: {
          type: 'object',
          properties: {
            query: {
              type: 'string',
              description: 'Search query (e.g., "5G charging CHF implementation", "handover procedures", "authentication security")'
            },
            max_results: {
              type: 'number',
              description: 'Maximum number of results to return (default: 5)',
              default: 5
            },
            series_filter: {
              type: 'array',
              items: { type: 'string' },
              description: 'Filter by specification series (e.g., ["32", "33", "38"])'
            },
            release_filter: {
              type: 'array',
              items: { type: 'string' },
              description: 'Filter by 3GPP release (e.g., ["Rel-16", "Rel-17"])'
            },
            include_content: {
              type: 'boolean',
              description: 'Include detailed specification content from TSpec-LLM (default: true)',
              default: true
            },
            format: {
              type: 'string',
              enum: ['detailed', 'summary', 'agent_ready'],
              description: 'Response format - agent_ready provides structured JSON optimized for AI agents',
              default: 'agent_ready'
            }
          },
          required: ['query']
        }
      };
    }
  • TypeScript interface defining the input arguments for the search_specifications tool.
    export interface SearchSpecificationsArgs {
      query: string;
      max_results?: number;
      series_filter?: string[];
      release_filter?: string[];
      include_content?: boolean;
      format?: 'detailed' | 'summary' | 'agent_ready';
    }
  • src/index.ts:101-102 (registration)
    Registration in the MCP server's CallToolRequestSchema handler: dispatches calls to 'search_specifications' to the SearchSpecificationsTool's execute method.
    case 'search_specifications':
      return await this.searchTool.execute(args as unknown as SearchSpecificationsArgs);
  • src/index.ts:78-78 (registration)
    Instantiation of the SearchSpecificationsTool instance in the server's initializeComponents method.
    this.searchTool = new SearchSpecificationsTool(this.apiManager);
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses the data sources (TSpec-LLM dataset and official metadata) and mentions the return format is 'optimized for AI agents,' which adds useful context. However, it doesn't address rate limits, authentication needs, error conditions, or pagination behavior that would be important for a search tool.

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 perfectly concise with two sentences that each earn their place. The first sentence establishes purpose and scope, while the second clarifies return values and agent optimization. There's zero wasted language or redundancy.

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?

For a search tool with 6 parameters, 100% schema coverage, and no output schema, the description is adequate but has gaps. It covers purpose and return types but lacks behavioral details like rate limits, error handling, or result structure. Without annotations or output schema, the agent must infer these from the tool name and parameters alone.

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?

Schema description coverage is 100%, so the schema already fully documents all 6 parameters. The description adds no additional parameter information beyond what's in the schema. The baseline score of 3 is appropriate when the schema does all the parameter documentation work.

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 action ('Search'), resource ('3GPP specifications'), data sources ('TSpec-LLM dataset and official metadata'), and return values ('actual specification content and structured metadata'). It distinguishes itself from siblings by focusing on search functionality rather than comparison, requirements finding, or detailed retrieval.

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 this tool should be used for searching specifications, but provides no explicit guidance on when to choose this tool versus its siblings (compare_specifications, find_implementation_requirements, get_specification_details). The context is clear but lacks specific alternatives or exclusions.

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/edhijlu/3gpp-mcp-server'

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