Skip to main content
Glama
jjunmomo

BaaS SMS/MCP Server

by jjunmomo

get_code_template_url

Generate CDN URLs for SMS/MMS integration code templates in various programming languages, frameworks, and deployment platforms. Simplify BaaS API implementation with ready-to-use, maintained templates and guides.

Instructions

Get URL for BaaS SMS/MMS integration code template from CDN

Perfect for: Getting optimized, maintained code templates without token overhead

Args:
    language: Programming language (javascript, python, php, java, go, csharp)
    framework: Optional framework (react, vue, django, laravel, fastapi, spring, etc.)
    deployment_platform: Optional platform (vercel, netlify, aws, docker, etc.)

Returns:
    CDN URL to markdown file with complete code examples and integration guide
    Templates include direct API calls to https://api.aiapp.link with /api/message/ endpoints

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deployment_platformNo
frameworkNo
languageYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Handler function implementing the 'get_code_template_url' tool logic. It constructs and returns a CDN URL for code templates based on language, framework, and platform parameters. Also decorated with @mcp.tool() for registration in the FastMCP server.
    @mcp.tool()
    async def get_code_template_url(
        language: str,
        framework: Optional[str] = None,
        deployment_platform: Optional[str] = None
    ) -> Dict[str, Any]:
        """
        Get URL for BaaS SMS/MMS integration code template from CDN
        
        Perfect for: Getting optimized, maintained code templates without token overhead
        
        Args:
            language: Programming language (javascript, python, php, java, go, csharp)
            framework: Optional framework (react, vue, django, laravel, fastapi, spring, etc.)
            deployment_platform: Optional platform (vercel, netlify, aws, docker, etc.)
        
        Returns:
            CDN URL to markdown file with complete code examples and integration guide
            Templates include direct API calls to https://api.aiapp.link with /api/message/ endpoints
        """
        try:
            language = language.lower()
            framework = framework.lower() if framework else None
            platform = deployment_platform.lower() if deployment_platform else None
            
            # CDN base URL with llms.txt optimization
            base_url = "https://cdn.mbaas.kr/templates/sms-mms"
            
            # Construct template path
            template_path = language
            if framework:
                template_path += f"/{framework}"
            else:
                template_path += "/vanilla"
            
            template_url = f"{base_url}/{template_path}.md"
            
            # Platform-specific integration guide
            integration_url = None
            if platform:
                integration_url = f"{base_url}/deployment/{platform}.md"
            
            # Supported combinations
            supported_languages = ["javascript", "python", "php", "java", "go", "csharp"]
            
            if language not in supported_languages:
                return {
                    "success": False,
                    "error": f"언어 '{language}'는 아직 지원되지 않습니다",
                    "supported_languages": supported_languages,
                    "error_code": "UNSUPPORTED_LANGUAGE"
                }
            
            return {
                "success": True,
                "language": language,
                "framework": framework,
                "deployment_platform": platform,
                "template_url": template_url,
                "integration_url": integration_url,
                "api_endpoint": "https://api.aiapp.link/api/message/",
                "cdn_info": {
                    "cache_duration": "24시간",
                    "last_updated": "자동 업데이트",
                    "version": "latest"
                },
                "configuration": {
                    "required_env_vars": ["BAAS_API_KEY"],
                    "installation_guide": f"{base_url}/setup/{language}.md",
                    "api_key_injected": bool(BAAS_API_KEY)
                },
                "message": f"{language} 템플릿 URL을 제공합니다. 토큰 최적화를 위해 CDN에서 직접 다운로드하세요."
            }
            
        except Exception as e:
            return {
                "success": False,
                "error": f"템플릿 URL 생성에 실패했습니다: {str(e)}",
                "error_code": "URL_GENERATION_ERROR"
            }
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it returns a CDN URL to markdown files, specifies the templates include direct API calls to specific endpoints, and mentions the templates are 'optimized' and 'maintained.' However, it doesn't cover potential rate limits, authentication needs, or error handling, leaving some gaps for a tool that interacts with external resources.

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 appropriately sized and front-loaded, starting with the core purpose, followed by usage guidelines, parameter details, and return information. Every sentence earns its place by adding value without redundancy, making it efficient and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (3 parameters, 1 required) and the presence of an output schema (which covers return values), the description is largely complete. It explains parameters well and provides usage context. However, it could benefit from more behavioral details like error cases or performance considerations, slightly reducing completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 0%, so the description must compensate fully. It successfully adds meaning beyond the schema by explaining each parameter's purpose: 'language' is for programming language with examples, 'framework' is optional with framework examples, and 'deployment_platform' is optional with platform examples. This provides clear context that the schema alone lacks.

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 specific action ('Get URL') and resource ('BaaS SMS/MMS integration code template from CDN'), distinguishing it from siblings like 'create_message_service_template' (creation), 'generate_direct_api_code' (code generation), and 'get_integration_guide' (guide retrieval). It explicitly mentions the purpose is to obtain optimized, maintained code templates without token overhead.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use this tool ('Perfect for: Getting optimized, maintained code templates without token overhead'), distinguishing it from alternatives like generating direct API code or getting integration guides. It clearly indicates this is for retrieving pre-built templates rather than creating or generating custom code.

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

Related 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/jjunmomo/BaaS-MCP'

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