Skip to main content
Glama

test_report

Idempotent

Needs sign-in (connect this server with OAuth, or pass an API key as the Authorization: Bearer header). Read this test session's backend observations and recorded browser evidence. Checks the uploaded build fingerprint and marks evidence stale if files changed. Backend counts do not prove correctness. Call before prepare_submission.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "test_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations, it discloses authentication requirements, the side effect of marking evidence stale when files changed, and a caveat that backend counts do not prove correctness. These are substantive behavioral details not available in the structured fields.

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 compact and every sentence contributes useful information. The auth requirement is front-loaded before the purpose, which is slightly less ideal, but overall it is well structured and not 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?

It covers authentication, sequencing, and a key side effect, but with no output schema it does not describe the structure or format of the returned observations and evidence. An agent knows when to call it and what argument to supply, but not what the report will look like.

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?

The schema has one required sessionId with 0% description coverage, so the description must carry meaning. It refers to 'this test session's' data, which implies sessionId identifies the session, but it adds no format or constraint details beyond that.

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 uses specific verbs and resources: it reads backend observations and browser evidence for a test session, checks the uploaded build fingerprint, and marks evidence stale. This clearly distinguishes it from preparation and evidence-recording siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says to call before prepare_submission, giving a clear sequencing rule. It does not describe when not to use it or name any alternative evidence-inspection tool, but the intended context is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources