Mark

Export Context Pack

export_context_pack

Read-onlyIdempotent

Exports this workspace's context pack: four markdown files (company, customer, offer, voice) built from what is saved in Mark. company has positioning, differentiators, doctrine, company facts and entities; customer has the active personas with pains, jobs, objections and their words; offer has what is sold today, what is planned, pricing, promises and claims to avoid; voice has tone, do and don't lines, example posts, posts that don't sound like the brand, and active content exclusions. Each file opens with the workspace name and export date, and marks a Brand section that is not confirmed. The files use the layout brand-interview reads, so they can seed another folder or workspace. Edits belong in Mark, not in the files. Does not change anything. Related: get_brand_context, update_brand_profile, save_strategy_item.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`files`	Yes
`appUrl`	Yes
`exportedAt`	Yes
`workspaceName`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 15, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: the exact file inventory, that each file opens with workspace name and export date, and that unconfirmed Brand sections are explicitly marked. It does not state where the files land or how they are delivered, which the output schema presumably covers.

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?

Front-loaded with the core action and artifact list, then the per-file breakdown, then constraints. It is dense and mostly earns its length, though 'Does not change anything' and 'Edits belong in Mark, not in the files' overlap slightly and the Related list is tacked on.

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?

For a zero-parameter export tool with an output schema, the description covers what will be produced, how the files are structured, and the mutation guardrail. The only notable omission is delivery mechanics (file paths vs. inline content), which the output schema can supply.

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 per the baseline this dimension defaults to 4. The description correctly adds no parameter detail because none exists, and nothing in the text misleads about inputs.

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 a specific verb and resource ('Exports this workspace's context pack') and immediately enumerates the four concrete artifacts produced (company, customer, offer, voice) with their contents. This makes it clearly distinguishable from sibling readers like get_brand_context or get_workspace, which return structured context rather than a file bundle.

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?

Gives a clear use case ('so they can seed another folder or workspace') and a guardrail ('Edits belong in Mark, not in the files'), which tells the agent this is a one-way snapshot rather than an editable round-trip. It lists related tools but does not explicitly say when to pick get_brand_context or update_brand_profile instead, so routing is left partly implicit.

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

All Mark tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?