FlagForge MCP Server

create_challenge

Add a challenge to an event with title, category, points, tags, and markdown description. Supports manual entry, mockups, or archiving self-made challenges.

Instructions

Create (write) a new challenge in an event — for manual entry, mockups, or archiving self-made challenges

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": {
      "event": "<event>",
      "title": "<title>",
      "category": "<category>"
    },
    "name": "create_challenge"
  }
}

Input Schema

Name	Required	Description
`tags`	No
`event`	Yes	Event UUID or slug
`title`	Yes
`points`	No
`category`	Yes
`external_id`	No	ID on the source platform, e.g. CTFd challenge id
`connection_info`	No	e.g. nc host 1337 or URL
`description_markdown`	No	Challenge description (markdown)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 5, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it explicitly flags the mutation nature via 'Create (write)' — the most important safety-relevant behavior for an agent weighing whether to call it. However, it does not disclose what happens after creation: no return value, no indication of whether the event must already exist, no idempotency or duplication behavior, and no permission requirements.

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 ~18-word sentence with the verb and resource front-loaded before the use cases. Every clause earns its place — the '(write)' qualifier, the resource scope, and the em-dash use-case context — with zero filler or repetition of schema content.

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 an 8-parameter mutation tool with no annotations and no output schema, the description covers purpose and when-to-use but omits critical invocation details: what the call returns, whether the event must pre-exist, and how failures surface. The missing return-value information is especially notable since no output schema exists to fill that 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 50%, leaving tags, title, points, and category undocumented in the schema, and the description does not compensate. The only parameter-level contribution is 'in an event,' which clarifies the event parameter's role; the remaining undocumented parameters receive no additional meaning from the description.

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

Purpose5/5

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

States the specific verb 'Create' reinforced by '(write)' and the resource 'a new challenge in an event.' The verb clearly differentiates from sibling CRUD tools (update_challenge, delete_challenge, get_challenge, list_challenges), and the explicit write flag distinguishes it from the read-only tools in the sibling set.

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

Usage Guidelines4/5

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

Names concrete use cases — 'manual entry, mockups, or archiving self-made challenges' — giving the agent clear situations in which to invoke it. It does not name alternatives or state when not to use it (e.g., that update_challenge is for modifying existing challenges), so no explicit exclusions are present.

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