Skip to main content
Glama
Sign In
Strands Agent MCP

Strands Agent MCP

by imgaray
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_skills

Retrieve all available skills for agents to enable integration with Amazon Q and MCP-compatible systems via the Strands Agent MCP server.

Instructions

list all available skills for agents

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_skills"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/strands_agent_mcp/server.py:48-54 (handler)
    The handler function for the 'list_skills' MCP tool. It returns a list of all registered skills from the agent_registry.skills.
    @mcp.tool(description="list all available skills for agents")
def list_skills() -> List[str]:
    """
    List all registered skills
    """
    return [skill for skill in agent_registry.skills]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/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 the full burden of behavioral disclosure. It states the tool lists skills but doesn't describe behavioral traits such as whether it's read-only, requires authentication, has rate limits, or what the output format looks like. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 a single, efficient sentence that directly states the tool's purpose without any wasted words. It is appropriately sized and front-loaded, making it easy for an agent to parse quickly. Every part of the sentence earns its place by conveying essential information.

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

Completeness2/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, no output schema), the description is minimal but adequate for basic understanding. However, it lacks context about behavioral aspects (e.g., read-only status, output format) and doesn't differentiate from siblings, making it incomplete for optimal agent guidance. With no annotations and no output schema, more detail would be beneficial.

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 the schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics beyond what the schema provides. A baseline of 4 is appropriate as it avoids redundancy while being complete 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 action ('list') and resource ('all available skills for agents'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this tool from its siblings (execute_agent and list_agents), which would require a 5. The description avoids tautology by not merely restating the tool name.

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 its siblings (execute_agent and list_agents) or any alternatives. It implies usage for retrieving skill information but lacks explicit context, prerequisites, or exclusions, leaving the agent with minimal direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools

Related Tools