Back to MCP tools

pre-alpha · v0.1.0

brief_save

Validate and atomically save answers to brief.json in an existing local project folder.

Inputs

Types and defaults come from source annotations. Constraints described below still apply; the schema is not runtime SDK output.

projectRequired
text
answersRequired
object
Full input schema
{
  "type": "object",
  "properties": {
    "project": {
      "type": "string"
    },
    "answers": {
      "type": "object",
      "additionalProperties": {}
    }
  },
  "required": [
    "project",
    "answers"
  ]
}

Outputs and behavior

Validate and atomically save answers to brief.json in an existing local project folder. Replaces the whole brief; omitted fields use brief_questions defaults. Returns answers, path, and a recommendation grounded in inventory and any attached reference breakdown. No media bytes, downloads, or model calls.

The tool description documents its results and behavior. An exact output schema is not supplied; fields not described here are unknown.

What touches the network

From this tool's description:

No media bytes, downloads, or model calls.

Network behavior beyond these details is not specified in the tool description.

Zing's network policy

Studying, rendering and memes run locally by default. Reference URL downloads require explicit consent. Requested model and font downloads are pinned by URL and SHA-256, cached locally and reported. Uoink is reached only through a peer you configure on your machine. Zing has no telemetry or analytics.

Source

Generated from the site's synced MCP inventory on every build. Descriptions and input schemas refer to this pinned source snapshot.

Source commit: d308dc3f9c2b42e305afd4d7d61e4bfa2f276bc4

Read the tool manifest