Skip to main content
Glama

TesterSwap

Find apps to test

find_apps_to_test
Read-onlyIdempotent

Find up to 20 apps you can test, with credits and minimum use time.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_apps_to_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
platformNo

Output Schema

NameRequiredDescriptionDefault
appsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/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 covered. The description adds genuine extra context — a hard cap of 20 results and that each result includes credits and minimum use time — but says nothing about how credits work, whether results change over time, or pagination behavior.

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; the result cap and the included metadata appear immediately. It is efficient, though its brevity is part of why parameter meaning is left uncovered.

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 no explanation, and the annotations cover safety. For a two-parameter discovery tool this is close to adequate, but the untranslated parameters and the vague 'credits and minimum use time' wording leave meaningful gaps.

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%: neither the 'query' string (max 100 chars) nor the 'platform' enum (android/ios) is documented in the schema. The description mentions no parameters at all, so it fails to compensate — an agent cannot learn that 'query' is a name/text filter or that 'platform' narrows to a store.

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 states a specific verb and resource ('Find ... apps you can test') and adds concrete scope: a 20-result cap and the fact that results carry credits and a minimum use time. It does not explicitly distinguish this discovery tool from siblings like list_my_apps or list_app, so it stops short of a 5.

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 statement of prerequisites or eligibility rules, and no routing to alternatives such as list_app or list_my_apps. The agent must infer the use case entirely from the title and the phrase 'apps you can test'.

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.