Skip to main content
Glama

crumple_traps

Read-only

Returns the attack traps used in crash-test runs, covering poisoned issues, malicious MCP servers, secret exfiltration, and destructive commands, with each modeled risk.

Instructions

The traps Crumple's crash test runs: each modelled on a real attack (poisoned issues, evil MCP servers, secret exfiltration, destructive commands), with its risk.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a non-mutating operation. The description adds useful domain context by saying the traps are modeled on real attacks and carry risk information, but it does not clarify whether the traps are static definitions, executable tests, or what form the risk data takes.

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?

The description is a single compact sentence, but it is syntactically elliptical and not front-loaded with a clear action. The colon-separated examples are informative but would benefit from an initial verb such as 'List' or 'Returns'.

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?

For a simple, no-parameter read-only tool, the description covers the domain meaning of the traps. However, with no output schema, it should ideally state that the tool returns a collection of trap definitions and what fields accompany each trap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics burden. The description appropriately focuses on what the returned traps represent rather than on inputs.

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?

The description identifies the resource (traps used in Crumple's crash tests) and describes their content, but it is a noun phrase rather than a clear verb+resource statement. An agent can infer this returns a catalog of attack-modeled traps, but cannot tell from the text alone whether it lists, retrieves, or runs them.

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 explicit guidance on when to use this tool, no prerequisites, and no comparison to alternatives such as crumple_scan or crumple_site. The intent is only implied by the content description.

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

Deploy Server

Other Tools