Skip to main content
Glama

함정 케이스 해설

explain_trap
Read-only

케이스 ID(TRAP-01~22)의 시나리오, 흔한 AI 오답, 정답, 근거를 반환합니다.

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": {
      "case_id": "<case_id>"
    },
    "name": "explain_trap"
  }
}

Input Schema

NameRequiredDescriptionDefault
case_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / case_id / pattern
      Previous value: -"^TRAP-(0[1-9]|1[0-9]|20)$"New value: +"^TRAP-(0[1-9]|1[0-9]|2[0-2])$"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that by enumerating the four content blocks returned, which is important given there is no output schema; it does not cover error behavior for out-of-range IDs, but the schema pattern mitigates that.

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 that names the input, its valid range, and the four returned components, with no filler. Every clause carries information the agent needs.

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

Completeness4/5

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

With no output schema, the description correctly carries the burden of describing return values and does so concretely for a single-parameter read-only tool. Only minor gaps remain, such as behavior on an invalid or unlisted case ID.

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?

There is one parameter with 0% schema description coverage, but the schema's regex already encodes the TRAP-01 through TRAP-22 range, which the description merely restates. The description does clarify that the ID selects a case whose explanation is returned, but it adds no further semantics such as whether unknown IDs error or return empty.

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 uses a specific verb ('반환합니다') and a specific resource (the scenario, common AI wrong answer, correct answer, and rationale for a TRAP case), and it names the ID range TRAP-01~22. An agent can tell this is a static educational lookup and not one of the regulatory/certification siblings, though the description never explicitly contrasts them.

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 only implied: the tool takes a case ID and returns the explanation, so an agent can infer it is for drilling into a specific trap case. There is no statement of when to prefer it over siblings like get_legal_basis, and no prerequisites or exclusions are given.

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.