Skip to main content
Glama

testmo_get_web_url

Generate a web URL to view a Testmo resource based on project, type, and ID.

Instructions

Generate a web URL for viewing a resource in Testmo.

Args: project_id: The project ID. resource_type: Type of resource (repositories, runs). resource_id: Resource ID (e.g., folder ID).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
resource_typeNorepositories
resource_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the testmo_get_web_url tool. It generates a web URL for viewing a resource (repositories, runs) in Testmo, optionally scoped by a group/resource ID.
    @mcp.tool()
    async def testmo_get_web_url(
        project_id: int,
        resource_type: str = "repositories",
        resource_id: int | None = None,
    ) -> dict[str, str]:
        """Generate a web URL for viewing a resource in Testmo.
    
        Args:
            project_id: The project ID.
            resource_type: Type of resource (repositories, runs).
            resource_id: Resource ID (e.g., folder ID).
        """
        url = f"{TESTMO_URL}/{resource_type}/{project_id}"
        if resource_id:
            url += f"?group_id={resource_id}"
        return {"url": url}
  • Function signature with typed parameters: project_id (int), resource_type (str, default 'repositories'), resource_id (int or None), and return type dict[str, str].
    async def testmo_get_web_url(
        project_id: int,
        resource_type: str = "repositories",
        resource_id: int | None = None,
  • Registered as an MCP tool via the @mcp.tool() decorator on the FastMCP instance defined in testmo/server.py.
    @mcp.tool()
  • Imports TESTMO_URL from config.py, which is used by the handler to construct the web URL.
    from ..config import FIELD_MAPPINGS, TESTMO_URL
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It states 'Generate a web URL,' implying a read-only operation, but does not mention any side effects, permissions, or limitations.

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 short and structured with an Args section, but it could be more concise. No extraneous information, but the format is a bit verbose.

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?

With an output schema present, return values need not be explained. However, the description omits details like whether the URL is full or relative, and any prerequisites. Adequate for a simple tool but not fully complete.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must add meaning. It provides brief descriptions for parameters (e.g., 'Type of resource (repositories, runs)') but does not detail all valid values or formats. Some value added, but insufficient.

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?

The description clearly states the tool generates a web URL for viewing a resource in Testmo, with a specific verb and resource. It distinguishes from sibling tools that return data objects rather than URLs.

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 vs. alternatives like testmo_get_case or testmo_get_run. It does not mention context 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