Skip to main content
Glama
weiwarren

AWS AgentCore MCP Server

by weiwarren
OverviewSchemaRelated ServersScoreDiscussions
Python

agentcore_gateway

Integrate external APIs and services with the AWS AgentCore framework to build AI agents with enterprise-grade security, observability, and scalability.

Instructions

Documentation on AgentCore Gateway for integrating external APIs and services.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • src/aws_agentcore_mcp_server/server.py:37-42 (handler)
    The agentcore_gateway tool handler function, decorated with @mcp.tool() for registration. It reads and returns the contents of the embedded 'gateway.md' documentation file providing information on AgentCore Gateway.
    @mcp.tool()
async def agentcore_gateway() -> str:
    """Documentation on AgentCore Gateway for integrating external APIs and services."""
    return pkg_resources.joinpath("content", "gateway.md").read_text(
        encoding="utf-8"
    )

Tool Definition Quality

C2.5/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. The description mentions 'documentation' which suggests a read-only informational function, but doesn't clarify whether this is actually a configuration tool, a testing interface, or something else. No information about authentication needs, rate limits, side effects, or return format is provided beyond the vague 'documentation' reference.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is a single sentence that's reasonably concise, but it's not particularly well-structured or front-loaded with the most critical information. While it doesn't waste words, it also doesn't efficiently communicate the tool's core function in a way that would help an AI agent quickly understand when to use it.

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 that the tool has 0 parameters, 100% schema coverage, and an output schema exists, the description doesn't need to explain parameters or return values. However, for a tool with no annotations and sibling alternatives, the description should do more to clarify the tool's specific role and behavioral characteristics. The current description is minimally adequate but leaves significant gaps about what the tool actually does.

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 there are no parameters to document. The description doesn't need to compensate for any parameter documentation gaps. A baseline of 4 is appropriate since there are no parameters requiring semantic explanation in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Documentation on AgentCore Gateway for integrating external APIs and services' is vague about what the tool actually does. It mentions 'documentation' which could imply a read-only informational tool, but doesn't specify a clear action verb or what resource it operates on. It distinguishes somewhat from siblings by mentioning 'gateway' and 'integrating external APIs', but doesn't clearly state the tool's function.

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?

No guidance is provided about when to use this tool versus the sibling tools (agentcore_code_interpreter, agentcore_identity, etc.). The description mentions 'integrating external APIs and services' which implies a specific context, but doesn't explicitly state when this tool should be selected over alternatives or what prerequisites might be needed.

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/weiwarren/agentcore-mcp-server'

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