Skip to main content
Glama

TesterSwap

Approve test

approve_test
Destructive

Approve a submitted test of your app and transfer its held credits to the tester.

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

Input Schema

NameRequiredDescriptionDefault
test_idYes

Output Schema

NameRequiredDescriptionDefault
stateYes
test_idYes

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 destructiveHint=true and idempotentHint=false, so the mutation profile is known. The description adds genuinely new information — that held credits are transferred to the tester — which the annotations do not convey. It still omits whether approval is reversible, what happens if the test is in the wrong state, or any auth/permission requirements for a financially consequential action.

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 front-loaded sentence with no filler; the verb, resource, and the side effect all appear immediately. Every clause earns its place.

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 needn't be described, and annotations cover safety signals. For a destructive, credit-moving action the definition is still thin on prerequisites (must the test be in submitted state?), reversibility, and failure behavior.

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?

One required parameter with 0% schema description coverage, so the description carries the burden and only partially does: "a submitted test" hints that test_id refers to a submitted test rather than an arbitrary one. It adds no format, sourcing, or error semantics beyond the name and uuid type in the schema.

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+resource ("Approve a submitted test of your app") and adds the key consequence ("transfer its held credits to the tester"). An agent can distinguish it from reject_test or get_test without opening a schema, though no sibling is named 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?

No explicit when-to-use or when-not-to-use guidance and no mention of alternatives such as reject_test or release_test. The phrase "a submitted test" weakly implies a precondition on test state, but nothing tells the agent what state is required or how to find eligible tests.

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.