Skip to main content
Glama

TesterSwap

Get test

get_test
Read-onlyIdempotent

Read your test and the in-app link for uploading your own screenshots.

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": "get_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
test_idYes

Output Schema

NameRequiredDescriptionDefault
urlYes
stateYes
app_idYes
reasonYes
creditsYes
test_idYes
app_nameYes
deadlineYes
platformYes
next_stepYes
claimed_atYes
approved_atYes
install_urlYes
tester_nameYes
minutes_usedYes
submitted_atYes
use_started_atYes
private_feedbackYes
minimum_use_minutesYes
finish_screenshot_statusYes
install_screenshot_statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the one genuinely non-obvious behavioral fact: the response includes an in-app link used for uploading your own screenshots. It says nothing about permissions or failure modes for an unknown test_id.

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?

A single tight sentence with the retrieval scope front-loaded and no filler. Every clause carries information.

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?

An output schema exists, so return values need not be explained, and annotations cover safety. Still, for a single-required-id lookup it leaves a gap around how to obtain a valid test_id and what 'test' refers to in this product's model.

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?

Only one parameter (test_id) with 0% schema description coverage; the schema supplies type, uuid format, and a strict pattern but no explanatory text. The name is self-explanatory and the description implies the test is 'yours', but it never says where a test_id comes from, which is the main thing the agent lacks.

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 gives a specific verb and resource ("read your test") and adds the notable payload of the in-app screenshot upload link. That distinguishes it from list-style siblings like get_app_tests and list_my_tests, though it does not name any sibling explicitly.

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 or when-not-to-use guidance and no alternative named. An agent must infer that it needs a test_id and that list_my_tests/get_app_tests is the way to discover one.

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.