Skip to main content
Glama
okareo-ai

Okareo MCP Server

Official
by okareo-ai

Generate Check

generate_check

Generate a check from a natural language description. AI creates the model prompt or Python code, then saves the check for evaluation.

Instructions

Generate a check from a natural language description. Uses AI to create the prompt template (model checks) or Python code (code checks), then saves the check.

    Use this when you only have a description of what to evaluate. When
    you already know the exact prompt template or Python code the check
    should use, call create_or_update_check directly instead. The
    generated prompt/code is returned in the response — review it and
    refine with create_or_update_check if needed.

    Args:
        name: Name for the generated check.
        description: Natural language description of what to evaluate
            (e.g., "check if the response is toxic"). The more specific
            the description, the better the generated check.
        output_type: "pass_fail" (boolean verdict), "score" (numeric), or
            "analysis" (free-form qualitative feedback; model checks only).
        check_type: "model" (LLM judge) or "code" (deterministic Python).
        requires_scenario_input: Set true when the evaluation must compare
            the output against the scenario input. The generated check
            will reference {scenario_input} and only works on runs whose
            scenarios provide it.
        requires_scenario_result: Set true when the evaluation must
            compare the output against the expected result. The generated
            check will reference {scenario_result} and only works on runs
            whose scenarios provide it.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
check_typeNomodel
descriptionYes
output_typeNopass_fail
requires_scenario_inputNo
requires_scenario_resultNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations show readOnlyHint=false, indicating a mutation. The description adds that AI generates the prompt/code, that the generated output is returned for review, and that scenario flags affect which runs the check works on. This goes beyond the bare annotations meaningfully, though it doesn't mention permissions or failure modes.

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?

The description is somewhat lengthy but well-structured: a clear purpose statement, then usage guidance, then a structured argument list. Every section adds necessary value, especially given the low schema coverage. It could be slightly tightened, but the length is justified by the tool's complexity.

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?

The description thoroughly covers the tool's purpose, when to use it, all parameters, the generated output returned for review, and dependencies on scenario flags. The presence of an output schema further reduces the need to describe return structure. It also points to create_or_update_check for refinement, providing a complete workflow.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description fully compensates. It explains all six parameters, including the allowed values for output_type ('pass_fail', 'score', 'analysis') and check_type ('model', 'code'), and clarifies the behavior of requires_scenario_input/result with example usage.

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 generates a check from a natural language description using AI, produces a prompt template or Python code, and saves the check. It explicitly distinguishes from sibling create_or_update_check by contrasting when to use each.

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

Usage Guidelines5/5

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

It provides explicit usage guidance: use this tool when only a description exists, and use create_or_update_check directly when the exact prompt/code is known. It also suggests refining the generated output with create_or_update_check, giving clear when-to and when-not-to context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/okareo-ai/okareo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server