Skip to main content
Glama

List human tasks

list_human_tasks

Lists criteria awaiting human raters in Verdict, helping you identify pending review tasks and optionally filter by rater.

Instructions

Criteria waiting on human raters.

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_human_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
raterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.8/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 disclosure burden and mostly fails it: nothing about read-only behavior, permissions, result shape, or pagination. The only behavioral hint is that results are limited to items awaiting human raters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the brevity comes from under-specification rather than economy—a five-word fragment with no verb or object. It is front-loaded only in the sense that there is nothing else.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with an undocumented parameter, no annotations, and no output schema, the description should at minimum explain what is returned and how 'rater' behaves. It provides none of that, leaving an agent unable to call it confidently.

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

Parameters1/5

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

Schema description coverage is 0% for the single 'rater' parameter, and the description never mentions it or explains whether it filters, scopes, or is optional. With low coverage the description must compensate, and it adds nothing.

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

Purpose2/5

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

The description is a noun-phrase fragment ("Criteria waiting on human raters") that never states the verb or what is actually listed. Combined with the name it can be guessed as 'list pending human review tasks', but the term 'Criteria' clashes with 'tasks' and leaves the resource ambiguous.

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 phrase 'waiting on human raters' implies a pending-review filter, which is a weak usage cue. There is no guidance on when to call this versus siblings like check_against_humans or submit_human_score, and no stated prerequisites or exclusions.

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