SapperMCP

Overview Schema Source Related Servers Discussions Admin

Sapper Flag

sapper_flag

Record captured flags with deduplication, then optionally submit them to the arena API and update their recorded, submitted, or rejected status.

Instructions

Record a captured flag (deduped). With submit=True also sends it via the arena API and updates the fact's status (recorded -> submitted/rejected).

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": {
      "value": "<value>"
    },
    "name": "sapper_flag"
  }
}

Input Schema

Name	Required	Default
`store`	No	.sapper
`title`	No
`value`	Yes
`submit`	No
`creator`	No	mcp
`challenge`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

C2.9/5.0

Behavior3/5

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

With no annotations, the description does carry useful behavioral detail: deduplication is applied, and submit=True triggers an external arena API call plus a status transition (recorded -> submitted/rejected). It does not say what happens to a duplicate (returned, ignored, or error), what authentication the arena submission needs, or whether submission is retryable after a rejection.

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

Conciseness4/5

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

Two short sentences, front-loaded with the core action and the conditional side effect. Nothing is padded, though the parenthetical status notation is a bit terse for an agent to parse.

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?

An output schema exists, so return values need not be described. But for a 6-parameter mutation tool with zero annotation and zero schema-description coverage, leaving four parameters and the duplicate-handling behavior undocumented is a substantial gap.

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 supply meaning; it only touches value (implicitly) and submit. The store, title, creator, and challenge parameters are completely unexplained, including what challenge refers to and how creator affects attribution.

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 names a specific verb and resource ("Record a captured flag") and adds a deduplication qualifier, so an agent can tell what the tool does. It does not differentiate from plausibly similar siblings such as sapper_capture or sapper_fact, which keeps it from a 5.

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 statement of when to use this tool versus alternatives, nor any exclusions or prerequisites. The only usage signal is implicit in the word "captured flag".

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

Deploy Server