Skip to main content
Glama
Sign In
zetesis

zetesis

by reutavidan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

check_evaluation

Read-only

Retrieve the completed result of a deep Zetesis evaluation using its job ID, including the reading and dossier link.

Instructions

Get the result of a full (deep) Zetesis dossier started earlier. Returns the reading and the rendered dossier link once it is ready.

Args: job_id: the id returned by evaluate_claim for a deep evaluation.

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": {
      "job_id": "<job_id>"
    },
    "name": "check_evaluation"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true and openWorldHint=true. The description adds that the result is returned once ready, hinting at polling behavior, which is beyond annotations. No contradictions.

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?

Description is extremely concise: two sentences plus an Args line. It front-loads the main purpose and provides necessary detail without waste.

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

Completeness5/5

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

For a polling tool with one parameter and an output schema, the description covers what to expect (reading and dossier link) and how to get the job_id. Combined with annotations and output schema, it is complete.

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?

Schema has 0% description coverage. The description compensates by explaining that job_id is the id returned by evaluate_claim for a deep evaluation, adding crucial context for correct usage.

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 clearly states the tool gets the result of a full dossier started earlier, and mentions it returns reading and rendered dossier link. It explicitly references sibling 'evaluate_claim' for job_id, distinguishing the tool's role.

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?

The description specifies that job_id comes from evaluate_claim for a deep evaluation, implying a chained usage. It does not explicitly list when not to use, but the context is clear.

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

Deploy Server

Other Tools