Skip to main content
Glama

get_result

Retrieve test run results using a specific code and hash identifier from the QASE test management platform.

Instructions

Get test run result by code and hash

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYes
hashYes

Implementation Reference

  • MCP server tool call handler for 'get_result': parses input args with GetResultSchema and delegates to getResult function.
    .with({ name: 'get_result' }, ({ arguments: args }) => {
      const { code, hash } = GetResultSchema.parse(args);
      return getResult(code, hash);
    })
  • Zod schema defining input for get_result tool: requires 'code' and 'hash' strings.
    export const GetResultSchema = z.object({
      code: z.string(),
      hash: z.string(),
    });
  • src/index.ts:150-154 (registration)
    Tool registration in ListToolsRequestSchema handler, specifying name, description, and input schema.
    {
      name: 'get_result',
      description: 'Get test run result by code and hash',
      inputSchema: zodToJsonSchema(GetResultSchema),
    },
  • Core getResult function: pipes client.results.getResult through toResult transformer.
    export const getResult = pipe(
      client.results.getResult.bind(client.results),
      toResult,
    );
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 states it's a read operation ('Get'), but doesn't disclose behavioral traits like error handling (e.g., what happens if code/hash is invalid), authentication needs, rate limits, or response format. The description is minimal and lacks critical operational context.

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 extremely concise (one short sentence) and front-loaded with the core purpose. There is no wasted verbiage, making it efficient for quick scanning.

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?

Given the tool has 2 required parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what a 'test run result' entails, how to obtain the code/hash, or what the return value looks like. For a retrieval tool with no structured support, more context is needed.

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 description coverage is 0%, so the description must compensate. It mentions parameters 'code and hash' but provides no semantic meaning (e.g., what these identifiers represent, their format, or examples). This adds minimal value beyond the schema's structural definition.

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

Purpose4/5

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

The description clearly states the action ('Get') and the resource ('test run result'), specifying it's retrieved by 'code and hash'. This distinguishes it from sibling tools like 'get_results' (plural) which likely returns multiple results. However, it doesn't explicitly contrast with other 'get_' tools like 'get_case' or 'get_run'.

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. It doesn't mention prerequisites (e.g., needing a valid code/hash), exclusions, or comparisons to similar tools like 'get_results' or 'get_run'. The description implies usage only when you have both identifiers.

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/rikuson/mcp-qase'

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