Kopern

kopern_create_grading_suite

Create a grading suite with test cases to evaluate an agent's behavior against expected outcomes for each input prompt.

Instructions

Create a grading suite with test cases on an agent. Each case has an input prompt and expected behavior for evaluation.

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>",
      "cases": "<cases>"
    },
    "name": "kopern_create_grading_suite"
  }
}

Input Schema

Name	Required	Description
`name`	No	Suite name (optional)
`cases`	Yes	Test cases
`agent_id`	Yes	The agent ID or name
`description`	No	Suite description (optional)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.0.5Apr 12, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations declare readOnlyHint=false and idempotentHint=false, and description aligns as a create operation. However, description adds no extra side effects or behavioral details beyond the obvious creation.

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?

Two sentences, no filler, front-loaded with the action.

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

Completeness3/5

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

Covers core purpose and cases structure, but omits return value and any usage prerequisites. Since no output schema exists, some expectation of return info would help.

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?

All 4 params have schema descriptions (100% coverage), so description adds little new. It summarizes cases but the schema already documents each field.

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 'Create a grading suite with test cases on an agent' – a specific verb+resource. Distinguishes from siblings like run_grading and get_grading_results by focusing on creation.

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?

No guidance on when to use vs alternatives. No mention of prerequisites or relationship to run_grading.

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