Kopern

kopern_run_grading

Execute grading suites on AI agents, running test cases against defined criteria and returning detailed scores to evaluate agent performance.

Instructions

Run a grading suite on an agent. Executes all test cases, evaluates with configured criteria, returns detailed scores. Uses YOUR API keys.

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>",
      "suite_id": "<suite_id>"
    },
    "name": "kopern_run_grading"
  }
}

Input Schema

Name	Required	Description	Default
`agent_id`	Yes	The agent ID or name
`suite_id`	Yes	The grading suite ID

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.0.5Apr 12, 2026

TDQS

A4/5.0

Behavior4/5

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

The annotations are minimal (readOnlyHint=false, openWorldHint=true), so the description adds meaningful context by disclosing that the tool executes test cases, evaluates, returns detailed scores, and 'Uses YOUR API keys'—an important external side-effect. It does not describe persistence or cost details, but it goes beyond the annotations without contradicting them.

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 short sentences, front-loaded with the primary purpose, and every clause contributes meaning. It avoids redundancy with the schema and is easy to parse quickly.

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 simple two-parameter tool, the description covers the main action and return value ('detailed scores') and includes the key caveat about API key usage. It does not describe output structure, but since no output schema is present and siblings cover related retrieval, this is reasonably complete.

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?

The schema already provides 100% coverage for both parameters with clear descriptions for agent_id and suite_id. The tool description does not add extra parameter-level semantics (e.g., formats, constraints, or usage patterns), so the baseline of 3 is appropriate.

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 a specific action ('Run a grading suite') and target ('an agent'), and distinguishes itself from siblings like get_grading_results (retrieval) and create_grading_suite (creation). The phrase 'Executes all test cases, evaluates with configured criteria, returns detailed scores' nails the scope.

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

Usage Guidelines3/5

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

The description implies when to use the tool—when you need to execute a grading suite—but it does not explicitly contrast with alternatives such as kopern_get_grading_results for retrieving results or kopern_list_grading_runs for listing runs. It provides some context via 'Uses YOUR API keys' but lacks explicit when/when-not guidance.

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