Skip to main content
Glama

agentcore_tools

Integrate tools with AWS AgentCore agents to build production-ready AI agents with enterprise-grade security, observability, and scalability.

Instructions

Documentation on integrating tools with AWS AgentCore agents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Implementation of the agentcore_tools handler function, which returns the content of tools.md documentation file using the @mcp.tool() decorator for registration.
    @mcp.tool()
    async def agentcore_tools() -> str:
        """Documentation on integrating tools with AWS AgentCore agents."""
        return pkg_resources.joinpath("content", "tools.md").read_text(
            encoding="utf-8"
        )
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 only states that the tool provides documentation, implying a read-only operation, but fails to describe how the documentation is accessed, formatted, or any limitations (e.g., authentication needs, rate limits). This leaves significant gaps in understanding the tool's behavior.

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, clear sentence that efficiently states the tool's purpose without redundancy. It is appropriately sized and front-loaded, with no wasted words, though it could be more specific to enhance 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 has 0 parameters, 100% schema coverage, and an output schema exists, the description is minimally complete. However, it lacks depth for a tool that provides documentation, such as explaining the format or scope of the documentation, which could help the agent use it effectively.

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, and schema description coverage is 100%, so there are no parameters to document. The description does not need to compensate for any parameter gaps, making it adequate in this dimension without adding unnecessary details.

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

Purpose3/5

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

The description states the tool provides 'Documentation on integrating tools with AWS AgentCore agents,' which gives a general purpose but lacks specificity. It doesn't clearly distinguish this from sibling tools like agentcore_code_interpreter or agentcore_gateway, making it vague about what unique function it serves.

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 on when to use this tool versus alternatives. The description does not mention any context, prerequisites, or exclusions, leaving the agent with no information on appropriate usage scenarios among the sibling tools.

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