Skip to main content
Glama

Get evaluation

get_evaluation

Retrieve an evaluation by ID to view its status, scores, rationales, and pending human tasks, so you can track rubric-based scoring results and follow-up work.

Instructions

Fetch an evaluation by id (status, scores, rationales, pending human tasks).

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": {
      "id": "<id>"
    },
    "name": "get_evaluation"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; "Fetch" correctly implies a non-mutating read. The parenthetical listing of returned fields adds genuine behavioral value, but nothing is said about behavior on a missing id (error vs empty), permissions/authentication, or whether results are cached or paginated.

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?

One short sentence with the action front-loaded and the return payload tucked into a parenthetical; there is no filler or redundancy.

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 single-parameter read tool with no output schema and no annotations, the definition gives enough to call it correctly and even previews the response fields. The remaining gaps (id format, not-found behavior) are minor at this complexity level.

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

Parameters3/5

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

Schema description coverage is 0% for the single required parameter, so the description must compensate. It only conveys that the id identifies an evaluation, which is marginal added meaning over the schema's property name and type; no format, source, or example of the id is given.

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+resource ("Fetch an evaluation") and enumerates what the payload contains (status, scores, rationales, pending human tasks), which lets an agent distinguish this read-by-id tool from siblings like evaluate or list_human_tasks. It stops short of naming an explicit alternative, but the purpose is unambiguous.

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?

Usage is only implied: the phrase "by id" signals this is a direct-lookup tool, so an agent can infer that it should be used when the evaluation id is already known. There is no explicit when-to-use/when-not-to-use guidance and no mention of the retrieval-oriented siblings (e.g., list_human_tasks) that cover adjacent needs.

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