Skip to main content
Glama

Test Results

test_results
Read-only

Retrieve aggregated results for a specific test ID to analyze monitor performance and outcomes.

Instructions

Resultados agregados de un test (monitor).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "test_id": "<test_id>"
    },
    "name": "test_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
test_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

The readOnlyHint=true annotation already tells the agent this is a safe read, so the description's main added signal is that results are 'aggregated' rather than raw. It says nothing about aggregation granularity, time window, pagination, or what happens when a test has no attempts; with an output schema present, some of that burden is lifted, but the description still adds very little beyond the annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no filler, so nothing is wasted. However, brevity here comes at the cost of under-specification rather than deliberate economy, and the description is written in Spanish while the tool names and sibling catalog are English, adding a small comprehension burden.

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?

With one required parameter, an output schema, and a simple read-only annotation profile, this tool should be easy to describe, yet the definition omits the aggregation scope, the relationship to sibling result tools, and any identifier sourcing guidance. The output schema covers return values, but selection and invocation context remain incomplete.

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 single required parameter test_id (integer) is undocumented in the schema. The description only implies it identifies a test/monitor; it does not say where to obtain the id, whether it accepts an external or internal identifier, or what happens with an invalid id.

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 identifies the resource (aggregated results of a test) and parenthetically clarifies that 'test' means 'monitor', which helps map to the domain. But it lacks a verb (get/list/aggregate) and does not explain how it differs from the closely named siblings course_results and student_results, so an agent cannot confidently pick among the three.

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?

There is no when-to-use guidance, no mention of alternatives such as course_results or student_results, and no prerequisites or exclusions. The only hint is the parenthetical 'monitor', which implies the test_id refers to a monitor rather than a plain test, but this is inference, not stated guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.