Skip to main content
Glama
daekeun-ml

PowerPoint Translator

by daekeun-ml
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

list_supported_models

Retrieve a list of supported AWS Bedrock model IDs for PowerPoint presentation translations, ensuring compatibility with the translation service.

Instructions

List all supported AWS Bedrock models for translation.

Returns: List of supported model IDs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • mcp_server.py:376-388 (handler)
    The handler function that implements the list_supported_models tool. It is registered via the @mcp.tool() decorator and returns a formatted list of supported AWS Bedrock models from Config.SUPPORTED_MODELS.
    @mcp.tool()
def list_supported_models() -> str:
    """
    List all supported AWS Bedrock models for translation.
    
    Returns:
        List of supported model IDs
    """
    models_text = "🤖 Supported AWS Bedrock models:\n\n"
    for model in Config.SUPPORTED_MODELS:
        models_text += f"• {model}\n"
    
    return models_text
  • ppt_translator/config.py:61-114 (helper)
    The SUPPORTED_MODELS class attribute in Config, which provides the list of AWS Bedrock models returned by the list_supported_models tool.
    SUPPORTED_MODELS = [
    # Amazon Nova models
    "amazon.nova-micro-v1:0",
    "amazon.nova-lite-v1:0", 
    "amazon.nova-pro-v1:0",
    "amazon.nova-premier-v1:0",
    
    # Anthropic Claude models
    "anthropic.claude-3-sonnet-20240229-v1:0",
    "anthropic.claude-3-haiku-20240307-v1:0",
    "anthropic.claude-3-5-sonnet-20240620-v1:0",
    "anthropic.claude-3-5-sonnet-20241022-v2:0",
    "anthropic.claude-3-5-haiku-20241022-v1:0",
    "us.anthropic.claude-3-5-sonnet-20240620-v1:0",
    "us.anthropic.claude-3-5-sonnet-20241022-v2:0",
    "us.anthropic.claude-3-5-haiku-20241022-v1:0",
    "us.anthropic.claude-3-7-sonnet-20250219-v1:0",
    "us.anthropic.claude-opus-4-20250514-v1:0",
    "us.anthropic.claude-sonnet-4-20250514-v1:0",
    "us.anthropic.claude-opus-4-1-20250805-v1:0",

    # Meta Llama models
    "meta.llama3-8b-instruct-v1:0",
    "meta.llama3-70b-instruct-v1:0",
    "us.meta.llama3-1-8b-instruct-v1:0",
    "us.meta.llama3-1-70b-instruct-v1:0",
    "us.meta.llama3-2-1b-instruct-v1:0",
    "us.meta.llama3-2-3b-instruct-v1:0",
    "us.meta.llama3-2-11b-instruct-v1:0",
    "us.meta.llama3-2-90b-instruct-v1:0",
    "us.meta.llama3-3-70b-instruct-v1:0",
    "us.meta.llama4-scout-17b-instruct-v1:0",
    "us.meta.llama4-maverick-17b-instruct-v1:0",
    
    # DeepSeek models 
    "deepseek.r1-v1:0",
    "us.deepseek.r1-v1:0",        
    
    # Mistral models
    "mistral.mistral-7b-instruct-v0:2",
    "mistral.mixtral-8x7b-instruct-v0:1",
    "mistral.mistral-large-2402-v1:0",
    "mistral.mistral-small-2402-v1:0",
    "mistral.pixtral-large-2502-v1:0",
    
    # Cohere models
    "cohere.command-r-v1:0",
    "cohere.command-r-plus-v1:0",
    
    # AI21 models 
    "ai21.jamba-1-5-large-v1:0",
    "ai21.jamba-1-5-mini-v1:0",
    "ai21.jamba-instruct-v1:0",
]
  • mcp_server.py:376-388 (registration)
    The @mcp.tool() decorator registers the list_supported_models function as an MCP tool.
    @mcp.tool()
def list_supported_models() -> str:
    """
    List all supported AWS Bedrock models for translation.
    
    Returns:
        List of supported model IDs
    """
    models_text = "🤖 Supported AWS Bedrock models:\n\n"
    for model in Config.SUPPORTED_MODELS:
        models_text += f"• {model}\n"
    
    return models_text

Tool Definition Quality

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states the return format ('List of supported model IDs'), which is helpful, but doesn't describe other behavioral traits like whether the list is static or dynamic, if there are rate limits, authentication requirements, or how the data is structured. For a tool with zero annotation coverage, this leaves significant gaps in understanding operational characteristics.

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 and well-structured: one sentence states the purpose, and a second clarifies the return value. Every sentence earns its place by providing essential information without redundancy. It's front-loaded with the core functionality and efficiently communicates necessary details.

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 simplicity (0 parameters, read-only operation) and the presence of an output schema (which handles return value documentation), the description is reasonably complete for basic use. However, with no annotations and siblings that suggest a translation workflow, it could benefit from more context about how this tool fits into that workflow or any behavioral constraints. The description covers the minimum viable information but lacks depth for optimal agent guidance.

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

Parameters4/5

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

The tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the lack of inputs. The description doesn't need to compensate for any parameter gaps. It appropriately doesn't mention parameters, focusing instead on the output. This meets the baseline expectation for a parameterless tool.

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: 'List all supported AWS Bedrock models for translation.' This specifies the verb ('List'), resource ('supported AWS Bedrock models'), and domain context ('for translation'). It distinguishes from siblings like 'list_supported_languages' by focusing on models rather than languages. However, it doesn't explicitly differentiate from other list/query tools beyond the domain specificity.

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, timing considerations, or how it relates to sibling tools like 'translate_powerpoint' or 'translate_specific_slides' that might depend on model selection. The agent must infer usage from the purpose alone without explicit direction.

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/daekeun-ml/ppt-translator'

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