Skip to main content
Glama

TesterSwap

Get app tests

get_app_tests
Read-onlyIdempotent

Read tests and private feedback for one of your apps.

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": {
      "app_id": "<app_id>"
    },
    "name": "get_app_tests"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idYes

Output Schema

NameRequiredDescriptionDefault
testsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds one genuinely new behavioral fact: the result includes private feedback, not just tests. It says nothing about volume, pagination, or whether tests and feedback are interleaved or separate sections.

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?

A single front-loaded sentence with no filler words; every term (read, tests, private feedback, one app) carries meaning. It is efficient, though its brevity shades into under-specification rather than optimal sizing.

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 the safety profile. However, for a tool whose name promises "tests" and whose description adds "private feedback", the agent is left unsure what a "test" record contains, whether results are paginated, and how feedback relates to tests.

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?

There is a single parameter, app_id, with 0% schema description coverage, so the schema provides only a uuid format and pattern. The description's "one of your apps" confirms the parameter selects a single app rather than a list, but adds no further semantics such as which app IDs are valid or what happens with an unknown ID.

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?

States a specific verb ("Read") and a specific resource ("tests and private feedback"), scoped to "one of your apps". This is clear enough to distinguish it from a broad listing tool like list_my_tests, but it never names or contrasts 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 guidance, no exclusions, and no named alternative. The phrase "for one of your apps" faintly implies per-app retrieval versus an account-wide listing, but the agent must infer that from context rather than from stated guidance.

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.