Kopern

kopern_export_agent

Read-only

Export an AI agent's full configuration including skills, tools, and grading suites as a portable JSON object for backup or transfer.

Instructions

Export an agent as a portable JSON object (agent config, skills, tools, extensions, grading suites with cases). Use kopern_import_agent to re-import. No LLM cost.

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": {
      "agent_id": "<agent_id>"
    },
    "name": "kopern_export_agent"
  }
}

Input Schema

Name	Required	Description	Default
`agent_id`	Yes	The agent ID to export

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.0.5Apr 12, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so read-only is known. The description adds useful behavioral details: 'No LLM cost' and the specific scope of the exported JSON, going beyond what annotations provide.

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?

The description is two concise sentences, front-loaded with the primary action and enriched with only essential details—the companion tool and cost note. Every word earns its place.

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

Completeness5/5

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

For a simple, read-only export tool with one parameter and no output schema, the description covers the purpose, scope, companion import tool, and cost. No critical information is missing.

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?

Schema description coverage is 100% with the single agent_id parameter clearly described. The tool description does not add parameter-specific details beyond the schema, so the baseline score of 3 applies.

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?

The description clearly states the tool exports an agent as a portable JSON object, listing the included components (config, skills, tools, extensions, grading suites). It distinctively uses the verb 'export' and differentiates from siblings like get_agent and import_agent.

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?

The description explicitly points to kopern_import_agent as the counterpart for re-importing, and notes 'No LLM cost,' providing context on when this tool is appropriate. It does not explicitly exclude alternatives like get_agent, but the purpose is clear enough.

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