Skip to main content
Glama

Validate rubric

validate_rubric

Validates a rubric in JSON or YAML, fills in defaults, and returns the result to catch mistakes before running an evaluation.

Instructions

Validate a rubric (JSON object or YAML string) and return it with defaults filled in. Use before evaluate to catch mistakes.

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": {
      "rubric": "<rubric>"
    },
    "name": "validate_rubric"
  }
}

Input Schema

NameRequiredDescriptionDefault
rubricYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully states that validation returns the rubric with defaults filled in, but it does not clarify side effects, whether the rubric is saved, or how validation errors are surfaced.

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 compact sentences with no filler. The core action and usage guidance are front-loaded and easy to scan.

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 one-parameter validation tool, it covers the essential input formats, return behavior, and intended usage. It could be more complete by explaining invalid-input behavior or confirming that validation is non-mutating.

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

Parameters4/5

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

The schema has 0% description coverage for the single 'rubric' parameter, so the description must compensate. It does so by explaining that the argument may be a JSON object or a YAML string, adding meaning beyond the raw anyOf types in the schema.

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 gives a specific verb and resource ('Validate a rubric') and adds the input formats and return behavior. It also distinguishes this from 'evaluate' by saying it should be used before evaluation to catch mistakes.

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?

It clearly says to use this before 'evaluate' to catch mistakes, which gives the agent a concrete usage context. It does not explicitly describe when not to use it or name alternatives such as create_rubric, so it falls short of full 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.