Skip to main content
Glama

TesterSwap

Send back or decline test

reject_test
Destructive

Send back or decline a submitted test with a reason. A first non-abuse refusal allows one fix within 24 hours.

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>",
      "reason": "<reason>"
    },
    "name": "reject_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
abuseNo
reasonYes
test_idYes

Output Schema

NameRequiredDescriptionDefault
stateYes
test_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and non-idempotent, so the mutation profile is covered; the description adds real value beyond them by disclosing the consequence: a first non-abuse refusal grants one fix attempt within 24 hours. It stops short of saying what happens to the test's status after the 24-hour window or how an abuse refusal differs in effect.

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?

Two short sentences with zero filler, the action stated first and the policy caveat second. Nothing could be removed without losing 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 no explanation, and the destructive annotation covers the safety profile. Still, for a three-parameter destructive tool at 0% schema coverage, the undefined abuse flag and the unspecified post-decline state leave gaps an agent would want filled before calling.

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?

Schema description coverage is 0%, so the description must carry the burden for three parameters. It clarifies that a 'reason' is required, and the phrase 'non-abuse refusal' hints at the abuse flag's significance, but it never explains what abuse=true does, what default false implies, or any format expectations for test_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?

The description gives a specific verb pair and resource: 'Send back or decline a submitted test with a reason.' That is far beyond a restatement of the name and makes the action immediately recognizable. It does not explicitly name approve_test as the opposite path, so sibling differentiation is implied rather than stated.

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

Usage Guidelines3/5

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

Usage is implied by 'decline a submitted test', and the second sentence supplies a concrete policy context (one fix within 24 hours) that shapes when this is appropriate. However, there is no explicit statement of when not to use it, no mention of the approve_test alternative, and no prerequisites such as required reviewer role.

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.