Skip to main content
Glama

resource_test_adapter

Destructive

Invoke a resource's exported bakeryAiTest(action, data) adapter on client or server side to run targeted tests with custom data, player, or server context.

Instructions

Call a resource's exported bakeryAiTest(action, data) adapter on the client or server side

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": {
      "resource": "<resource>",
      "action": "<action>"
    },
    "name": "resource_test_adapter"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNo
sideNoclient
actionYes
playerNo
serverNo
resourceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=false, so the safety profile is carried structurally. The description adds that execution can happen on the client or server side, which is useful context beyond annotations, but it never explains what 'destructive' means here — arbitrary adapter actions may mutate or destroy game state — nor whether authorization or a running server is required. That leaves a meaningful gap for a destructive tool, though not a contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with no filler, front-loaded with the verb and target. However, its brevity comes at the cost of under-specification rather than efficiency — the parenthetical signature is the only concrete detail provided.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, six-parameter tool with nested payloads, an unresolvable identifier (`bakeryAiTest`) and no output schema, the description is too thin. It leaves the agent unable to predict results or understand the player/server parameters, so the definition is incomplete relative to the tool's complexity.

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% across 6 parameters, so the description must compensate and it only partially does: it names `action` and `data`, and implies `side` via 'client or server side'. The required `resource` parameter, `player`, and `server` are never explained, and nothing clarifies that `data` is an arbitrary nested payload passed through to the adapter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a verb ("Call") and a target ("a resource's exported bakeryAiTest(action, data) adapter"), which is more specific than a tautology, but the core object — what a 'bakeryAiTest adapter' is or does — is opaque jargon. An agent can tell it is invoking something on a resource, but not what kind of operation that actually performs.

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 guidance on when to use this tool versus siblings like test_execute_scenario, lua_eval, or resource_control. Nothing states prerequisites (does the resource need to export the adapter?), nor when the client vs server side should be chosen beyond the presence of a `side` parameter.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.