Skip to main content
Glama

get_dev_agent

Retrieve details about the Development Agent to access its capabilities and configuration within the MCP Agents server.

Instructions

Get information about the Development Agent

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function decorated with @mcp.tool('get_dev_agent') that implements the tool logic by returning the predefined dev_agent profile from AGENT_PROFILES.
    @mcp.tool("get_dev_agent", description="Get information about the Development Agent")
    def get_dev_agent() -> Dict:
        """Returns the Development Agent's profile, capabilities, and limitations."""
        return AGENT_PROFILES["dev_agent"]
  • The AGENT_PROFILES['dev_agent'] dictionary containing the profile, capabilities, limitations, and prompt returned by the get_dev_agent tool.
    "dev_agent": {
        "name": "Development Agent",
        "description": "A specialized AI agent for software development tasks",
        "capabilities": [
            "Write and review code in multiple programming languages",
            "Debug and troubleshoot technical issues",
            "Implement features and fix bugs",
            "Provide architecture and design recommendations",
            "Optimize performance and code quality",
            "Create and maintain technical documentation",
        ],
        "limitations": [
            "Cannot directly access production systems",
            "Cannot make deployment decisions without approval",
            "Should not modify database schemas without review",
            "Must follow established coding standards and practices",
        ],
        "prompt": "You are a senior software developer with expertise in multiple programming languages and frameworks. Focus on writing clean, maintainable, and efficient code. Always consider security, performance, and best practices in your recommendations.",
    },
  • The @mcp.tool decorator registering the get_dev_agent function as an MCP tool.
    @mcp.tool("get_dev_agent", description="Get information about the Development Agent")
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 'gets information', implying a read-only operation, but doesn't specify if it's safe, what data is returned, any rate limits, or authentication needs. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior and constraints.

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, clear sentence: 'Get information about the Development Agent'. It is front-loaded with the core action and resource, with no wasted words or extraneous details. This makes it highly efficient and easy to parse at a glance.

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 adequate. However, it lacks details on what information is retrieved, how it differs from sibling tools, or any behavioral context. With no annotations and a generic purpose, it could be more complete to aid in tool selection and usage.

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 input schema has 100% description coverage (though empty). The description doesn't need to add parameter details, as there are none to explain. It appropriately avoids unnecessary parameter information, earning a baseline score of 4 for not introducing confusion or redundancy.

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 'Get information about the Development Agent' clearly states the action (get) and target resource (Development Agent), providing basic purpose. However, it doesn't differentiate from sibling tools like 'get_po_agent' or 'get_qa_agent' beyond the agent type, nor does it specify what kind of information is retrieved. This makes it somewhat vague compared to more specific alternatives.

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 alternatives such as 'list_all_agents'. It doesn't indicate if this is for detailed info on a single agent, if it requires specific permissions, or any contextual prerequisites. Without such guidance, users must infer usage from 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