Skip to main content
Glama

testmo_get_project

Retrieve details of a specific Testmo project by providing its project ID.

Instructions

Get details of a specific Testmo project by ID.

Args: project_id: The project ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The testmo_get_project tool handler. It's an async function decorated with @mcp.tool() that takes a project_id integer and makes a GET request to /projects/{project_id} via _request.
    @mcp.tool()
    async def testmo_get_project(project_id: int) -> dict[str, Any]:
        """Get details of a specific Testmo project by ID.
    
        Args:
            project_id: The project ID.
        """
        result = await _request("GET", f"/projects/{project_id}")
        return result.get("result", result)
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states 'Get details,' implying a read operation, but does not explicitly confirm idempotence, safety, or potential side effects. No error/rate limit info is given.

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 concise, with a single-line purpose followed by a brief parameter listing. It is front-loaded and efficient, though it could include slightly more detail without becoming verbose.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (single integer parameter, output schema present), the description is mostly complete. The output schema likely covers return values, so the description only needs to clarify the input and purpose, which it does adequately.

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?

The input schema has 0% description coverage; the description adds only 'The project ID,' which essentially repeats the parameter title. No additional context like source, format, or constraints is provided beyond the schema.

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 'Get details of a specific Testmo project by ID,' which is a specific verb+resource. It distinguishes from sibling tools like testmo_list_projects (which lists all projects) and testmo_get_case (which gets a case).

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 using testmo_list_projects to obtain project IDs first. It also lacks context on prerequisites or conditions for use.

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