Skip to main content
Glama

List rubrics

list_rubrics

Retrieve stored rubrics to choose the right scoring criteria for evaluating text, files, or pages with Verdict.

Instructions

List stored rubrics.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_rubrics"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing beyond the operation itself. It does not disclose whether all rubrics or only some subset are returned, whether results are paginated, whether archived/draft rubrics are included, or what fields the listing contains.

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?

A single three-word sentence that is front-loaded and free of filler; nothing could be trimmed. Its brevity is efficient rather than padded, though it leaves the reader wanting more substance.

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?

This is a simple zero-parameter read tool with no output schema, so the bar is low, and the definition covers the basic operation. Still, an agent cannot tell what the response shape is or whether all rubrics are returned in one call, which matters for a listing endpoint.

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 tool takes zero parameters, so there is nothing for the description to clarify beyond the schema, which is why the baseline is 4. The wording "stored" is the only hint about the data universe being enumerated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"List stored rubrics" gives a concrete verb (list) and resource (rubrics), so there is no ambiguity about what the tool does. It does not, however, differentiate itself from rubric-related siblings such as create_rubric, fork_rubric, or validate_rubric, nor does it state the scope of the listing.

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?

The description contains no when-to-use guidance, no mention of alternatives, and no prerequisites. An agent can infer that this is the discovery step before evaluate or get_evaluation, but that inference comes entirely from sibling names, not from the definition.

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