Amazon Bedrock MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_imageC | Generate image(s) using Amazon Nova Canvas model. The returned data is Base64-encoded string that represent each image that was generated. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool 'generate_image' has a clear and distinct purpose that cannot be mistaken for any other tool in the set.
The single tool name 'generate_image' follows a verb_noun pattern, and with only one tool, consistency is inherently perfect. There are no other tools to compare against, so no inconsistencies can arise.
A single tool is too few for a server named 'Amazon Bedrock MCP Server', which suggests a broader scope related to Amazon Bedrock services. This minimal toolset feels thin and incomplete for the implied domain, limiting functionality to just image generation.
The tool surface is severely incomplete for the server's purpose. Amazon Bedrock includes multiple models and capabilities beyond image generation, such as text generation, embeddings, and model management. The single tool fails to cover these core aspects, leaving significant gaps that will cause agent failures.