Skip to main content
Glama

testmo_get_automation_source

Retrieve details of an automation source by providing its ID. Optionally include related entities.

Instructions

Get details of a specific automation source.

Args: automation_source_id: The automation source ID. expands: Related entities to include.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
automation_source_idYes
expandsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool handler function for 'testmo_get_automation_source'. It sends a GET request to /automation/sources/{automation_source_id} with optional expands parameter, and returns the 'result' sub-object from the response if present.
    @mcp.tool()
    async def testmo_get_automation_source(
        automation_source_id: int,
        expands: list[str] | None = None,
    ) -> dict[str, Any]:
        """Get details of a specific automation source.
    
        Args:
            automation_source_id: The automation source ID.
            expands: Related entities to include.
        """
        params: dict[str, Any] = {}
        if expands:
            params["expands"] = ",".join(expands)
        result = await _request(
            "GET",
            f"/automation/sources/{automation_source_id}",
            params=params if params else None,
        )
        return result.get("result", result)
  • The @mcp.tool() decorator registers this function as an MCP tool on the FastMCP server instance.
    @mcp.tool()
  • testmo/server.py:1-7 (registration)
    The MCP server instance (FastMCP) on which tools are registered via the @mcp.tool() decorator.
    from dotenv import load_dotenv
    from mcp.server.fastmcp import FastMCP
    
    load_dotenv()
    
    mcp = FastMCP("testmo-mcp")
  • testmo-mcp.py:17-17 (registration)
    The import that triggers tool registration by importing the automation module.
    import testmo.tools.automation  # noqa: F401
  • The _request helper function used by the tool handler to execute the HTTP request to the Testmo API.
    async def _request(
        method: str,
        endpoint: str,
        data: dict[str, Any] | None = None,
        params: dict[str, Any] | None = None,
    ) -> dict[str, Any]:
        async with _get_client() as client:
            response = await client.request(
                method=method,
                url=endpoint,
                json=data,
                params=params,
            )
            if response.status_code == 204:
                return {"success": True}
            if response.status_code >= 400:
                try:
                    error_body = response.json()
                except Exception:
                    error_body = response.text
                raise RuntimeError(
                    f"Testmo API error {response.status_code}: "
                    f"{json.dumps(error_body) if isinstance(error_body, dict) else error_body}"
                )
            return response.json()
Behavior2/5

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

No annotations provided, so description must disclose behavior. It only states 'Get details' and lists params. No mention of what happens on invalid ID, authentication needs, rate limits, or side effects. Very limited.

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?

Extremely concise at 3 lines, front-loaded with purpose. Every sentence serves a purpose, no filler.

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?

Despite having an output schema, the description does not mention what details are returned or any constraints. Lacks context for a tool with two parameters and many siblings. Incomplete for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%. Description repeats parameter names with minimal clarification: 'The automation source ID' is tautological; 'Related entities to include' adds some context for expands but is vague. Does not compensate for missing schema descriptions.

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

Purpose5/5

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

Description clearly states 'Get details of a specific automation source' with a specific verb and resource. It distinguishes from sibling tools like testmo_list_automation_sources which lists all sources.

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 on when to use this tool versus alternatives (e.g., list_automation_sources). The description does not specify context, prerequisites, or when not to use it.

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/strelec00/testmo-mcp'

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