Skip to main content
Glama

Submit human score

submit_human_score

Submit a human rater’s score for a rubric criterion waiting on human review, recording a numeric, ordinal, or binary result with optional rationale.

Instructions

Submit a human rater's score for a criterion that is waiting on a human. Score is a number on the criterion scale or an ordinal/binary label.

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": {
      "evaluationId": "<evaluationId>",
      "criterionId": "<criterionId>",
      "raterId": "<raterId>",
      "score": "<score>"
    },
    "name": "submit_human_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
scoreYes
raterIdYes
rationaleNo
criterionIdYes
evaluationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden. It discloses the waiting-criterion precondition and the accepted score format, but says nothing about permissions, whether a submitted score can be overwritten, validation failures, or what effect submission has on the evaluation.

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 front-loaded sentences with no filler. The first states the action and precondition, and the second clarifies the score format efficiently.

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

Completeness2/5

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

This is a mutation tool with five parameters, four required, no annotations, no output schema, and zero schema description coverage. The description covers the score value somewhat but omits parameter semantics and mutation outcomes, so it is not complete enough for confident invocation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for five undocumented parameters. It clarifies only the score parameter as a number on the criterion scale or an ordinal/binary label, leaving evaluationId, criterionId, raterId, and rationale without added meaning.

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?

The description uses a specific verb and resource: submit a human rater's score for a criterion waiting on a human. It clearly communicates the action and precondition, but does not explicitly distinguish itself from siblings such as list_human_tasks or check_against_humans.

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

Usage Guidelines3/5

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

The phrase 'criterion that is waiting on a human' implies the usage context, so an agent can infer when this tool applies. However, it provides no explicit when-not guidance, prerequisites, or routing to alternatives for finding pending human tasks.

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