Skip to main content
Glama

get_qa_agent

Retrieve details about the Quality Assurance Agent to access QA functionality within the MCP Agents server.

Instructions

Get information about the Quality Assurance Agent

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_qa_agent' tool, registered via @mcp.tool decorator. It returns the predefined QA agent profile dictionary containing name, description, capabilities, limitations, and prompt.
    @mcp.tool(
        "get_qa_agent", description="Get information about the Quality Assurance Agent"
    )
    def get_qa_agent() -> Dict:
        """Returns the QA Agent's profile, capabilities, and limitations."""
        return AGENT_PROFILES["qa_agent"]
  • The QA agent profile data used by the get_qa_agent tool handler.
    "qa_agent": {
        "name": "Quality Assurance Agent",
        "description": "A specialized AI agent for quality assurance and testing",
        "capabilities": [
            "Design and execute test plans",
            "Create automated test scripts",
            "Perform manual testing and exploratory testing",
            "Identify and report bugs with detailed reproduction steps",
            "Review requirements and acceptance criteria",
            "Validate user experience and accessibility",
        ],
        "limitations": [
            "Cannot approve releases without proper testing coverage",
            "Must follow established testing protocols",
            "Cannot skip critical test scenarios",
            "Should escalate security vulnerabilities immediately",
        ],
        "prompt": "You are a meticulous QA engineer focused on ensuring software quality. Your primary goal is to identify issues before they reach production. Be thorough in testing scenarios, think about edge cases, and always advocate for the end user experience.",
    },
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 the purpose without detailing traits like whether it's a read-only operation, authentication requirements, rate limits, or what the output includes. This is inadequate for a tool with zero annotation coverage.

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 with no wasted words. It's front-loaded and appropriately sized for a simple tool, making it easy to parse quickly.

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, no annotations, but with an output schema), the description is minimally adequate. It states the purpose but lacks details on behavioral traits or output format, which the output schema might cover, leaving some gaps in completeness.

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 fully documents the lack of inputs. The description doesn't need to add parameter details, and it doesn't contradict the schema, earning a baseline score above 3 due to the absence of parameters.

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's purpose ('Get information about the Quality Assurance Agent'), which is clear but vague. It uses a generic verb ('Get') without specifying what type of information is retrieved (e.g., configuration, status, details), and it doesn't differentiate from sibling tools like 'get_dev_agent' or 'list_all_agents' beyond the agent type.

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 doesn't mention prerequisites, context for usage, or comparisons to sibling tools such as 'get_dev_agent' or 'list_all_agents', leaving the agent to infer usage based on the tool name alone.

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/amajakai14/mcp-agents'

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