Skip to main content
Glama

find_implementation_requirements

Extract detailed 3GPP feature implementation requirements including mandatory/optional specifications, dependencies, and testing guidance for telecommunications development.

Instructions

Extract detailed implementation requirements for specific 3GPP features, including mandatory/optional requirements, dependencies, and implementation guidance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
featureYesThe feature or functionality to analyze (e.g., "CHF implementation", "5G handover", "SUCI privacy protection")
domainNoSpecific domain context (e.g., "charging", "security", "mobility", "radio")
complexity_levelNoImplementation complexity level (default: intermediate)intermediate
include_dependenciesNoInclude dependency analysis and prerequisite requirements (default: true)
include_testing_guidanceNoInclude testing and validation guidance (default: true)
formatNoResponse format - agent_ready provides structured JSON for AI agentsagent_ready

Implementation Reference

  • Main handler: executes the tool by querying the API manager for requirements and formatting the response in agent_ready, summary, or detailed format.
    async execute(args: FindImplementationRequirementsArgs) {
      try {
        const context = {
          domain: args.domain,
          complexity_level: args.complexity_level || 'intermediate'
        };
    
        const requirements = await this.apiManager.findImplementationRequirements(args.feature, context);
    
        const format = args.format || 'agent_ready';
    
        switch (format) {
          case 'agent_ready':
            return {
              content: [
                {
                  type: 'text',
                  text: JSON.stringify(this.formatForAgent(requirements, args), null, 2)
                }
              ]
            };
    
          case 'summary':
            return {
              content: [
                {
                  type: 'text',
                  text: this.formatSummary(requirements, args)
                }
              ]
            };
    
          case 'detailed':
          default:
            return {
              content: [
                {
                  type: 'text',
                  text: this.formatDetailed(requirements, args)
                }
              ]
            };
        }
    
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error finding implementation requirements: ${error instanceof Error ? error.message : 'Unknown error'}`
            }
          ],
          isError: true
        };
      }
    }
  • Tool definition including input schema for validation and tool metadata.
    getDefinition() {
      return {
        name: 'find_implementation_requirements',
        description: 'Extract detailed implementation requirements for specific 3GPP features, including mandatory/optional requirements, dependencies, and implementation guidance.',
        inputSchema: {
          type: 'object',
          properties: {
            feature: {
              type: 'string',
              description: 'The feature or functionality to analyze (e.g., "CHF implementation", "5G handover", "SUCI privacy protection")'
            },
            domain: {
              type: 'string',
              description: 'Specific domain context (e.g., "charging", "security", "mobility", "radio")'
            },
            complexity_level: {
              type: 'string',
              enum: ['basic', 'intermediate', 'advanced'],
              description: 'Implementation complexity level (default: intermediate)',
              default: 'intermediate'
            },
            include_dependencies: {
              type: 'boolean',
              description: 'Include dependency analysis and prerequisite requirements (default: true)',
              default: true
            },
            include_testing_guidance: {
              type: 'boolean',
              description: 'Include testing and validation guidance (default: true)',
              default: true
            },
            format: {
              type: 'string',
              enum: ['detailed', 'summary', 'agent_ready'],
              description: 'Response format - agent_ready provides structured JSON for AI agents',
              default: 'agent_ready'
            }
          },
          required: ['feature']
        }
      };
    }
  • src/index.ts:85-93 (registration)
    Registration in listTools handler: includes requirementsTool.getDefinition().
    this.server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          this.searchTool.getDefinition(),
          this.detailsTool.getDefinition(),
          this.compareTool.getDefinition(),
          this.requirementsTool.getDefinition()
        ]
      };
  • src/index.ts:110-112 (registration)
    Dispatch registration in callTool handler: routes to requirementsTool.execute.
    case 'find_implementation_requirements':
      return await this.requirementsTool.execute(args as unknown as FindImplementationRequirementsArgs);
  • Backend helper method in APIManager that performs the core search and extraction of implementation requirements using TSpec-LLM and 3GPP API.
    async findImplementationRequirements(feature: string, context?: {
      domain?: string;
      complexity_level?: 'basic' | 'intermediate' | 'advanced';
    }): Promise<{
      requirements: any[];
      related_specifications: SpecificationMetadata[];
      implementation_guidance: string[];
    }> {
      try {
        const searchQuery = `${feature} implementation requirements ${context?.domain || ''}`;
    
        // Search TSpec-LLM for implementation details
        const tspecResults = await this.tspecClient.searchSpecifications({
          query: searchQuery,
          max_results: 10
        });
    
        // Extract requirements from content
        const requirements = this.extractRequirements(tspecResults);
    
        // Find related specifications
        const relatedSpecs = await this.tgppClient.searchSpecifications(feature);
    
        // Generate implementation guidance
        const implementationGuidance = this.generateImplementationGuidance(
          feature,
          tspecResults,
          context
        );
    
        return {
          requirements,
          related_specifications: relatedSpecs,
          implementation_guidance: implementationGuidance
        };
    
      } catch (error) {
        throw new Error(`Failed to find implementation requirements: ${error instanceof Error ? error.message : 'Unknown error'}`);
      }
    }
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 mentions what the tool extracts (requirements, dependencies, guidance) but lacks critical behavioral details: it doesn't specify if this is a read-only operation, what data sources it queries, potential rate limits, authentication needs, or error handling. For a tool with 6 parameters and no annotations, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core purpose ('Extract detailed implementation requirements...') and lists key components. There's no wasted text, but it could be slightly more structured by explicitly separating the tool's function from its outputs for better clarity.

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 complexity (6 parameters, no output schema, no annotations), the description is moderately complete. It covers the what (extract requirements) and scope (3GPP features) but lacks context on how it operates, data sources, or output format. Without annotations or an output schema, more behavioral and usage details would improve completeness for effective agent use.

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%, meaning all parameters are well-documented in the input schema itself. The description adds minimal value beyond the schema by implying the tool analyzes features for implementation details, but it doesn't provide additional context on parameter interactions or usage examples. With high schema coverage, the baseline score of 3 is appropriate.

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: 'Extract detailed implementation requirements for specific 3GPP features' with specific components listed (mandatory/optional requirements, dependencies, implementation guidance). It uses the verb 'extract' with the resource 'implementation requirements' and scope '3GPP features.' However, it doesn't explicitly differentiate from sibling tools like 'compare_specifications' or 'get_specification_details,' which might also involve 3GPP specifications.

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 sibling tools or specify contexts where this tool is preferred, such as for implementation planning versus specification comparison. There's no indication of prerequisites or exclusions, leaving usage decisions 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/edhijlu/3gpp-mcp-server'

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