Skip to main content
Glama
okareo-ai

Okareo MCP Server

Official
by okareo-ai
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Get Okareo Templates

get_templates
Read-onlyIdempotent

Get ready-to-use prompt templates for building Okareo test scenarios, checks, and drivers. Works offline.

Instructions

Retrieve prompt templates for common Okareo patterns.

    Returns starter templates for building Okareo test components. These
    templates are served as static content from the MCP — no network calls
    required. Always available, even in air-gapped environments.

    Available templates:
    - basic_scenario: Template for creating a basic Okareo test scenario
    - boolean_check_prompt: Template for a pass/fail (boolean) check prompt
    - score_check_prompt: Template for a scored check prompt
    - check_code: Template for a code-based check (Python function)
    - target_validate_check_prompt: Template for validating target output
    - driver_prompt: Template for a Driver persona prompt
    - driver_voice_extension_prompt: Template for voice interaction extensions
    - analysis_check_prompt: Template for an analysis check (qualitative feedback)

    Args:
        template_name: Template identifier to retrieve. Omit to get a
            lightweight listing of all available templates (names and
            descriptions only). Provide a template_name to get the full
            template content. Valid values: basic_scenario,
            boolean_check_prompt, score_check_prompt, check_code,
            target_validate_check_prompt, driver_prompt,
            driver_voice_extension_prompt, analysis_check_prompt.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
template_nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint), the description adds valuable behavioral context: templates are served as static content with no network calls, always available even in air-gapped environments. It also explains the differing behavior when the parameter is omitted vs provided, which is not captured by annotations.

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 well-structured with an introductory sentence, a note on static availability, a bulleted list of templates, and an Args block. Despite being long, it is concise because every line adds necessary information. It is front-loaded with the primary purpose and does not contain fluff.

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 tool has a single optional parameter and an output schema. The description explains what the output will be in both modes (listing or full content) and lists all valid template names. Given the output schema exists, no further return-value detail is needed. The description is complete for the tool's simplicity.

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?

The input schema provides zero description coverage for template_name (just a title and type). The tool description compensates fully by documenting the parameter, listing all valid values, and explaining the behavior when omitted. This is exemplary parameter documentation.

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's function: 'Retrieve prompt templates for common Okareo patterns.' It uses a specific verb (retrieve) and resource (prompt templates), and the list of available templates further distinguishes this tool from any sibling tool. No ambiguity about what the tool does.

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 provides clear usage guidance: omit template_name to get a listing, or provide it to get full template content. It also explains the static, offline nature of the content. However, it does not explicitly compare to alternative tools or state when not to use it, though no sibling tool serves the same purpose.

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