Skip to main content
Glama

Validate Research Record

validate_research_record
Read-onlyIdempotent

Validates a typed research record for required source metadata and extracted facts, returning issues to check before passing the record to dossier-building tools.

Instructions

Validate that a typed research record has source metadata and extracted facts. Returns a validation result with a list of issues. Use when checking a research record before passing it to dossier-building tools. Pass the record from build_research_record output.

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": {
      "dishName": "<dishName>",
      "query": "<query>",
      "sources": "<sources>",
      "extractedFacts": "<extractedFacts>",
      "uncertainty": "<uncertainty>",
      "confidence": "<confidence>",
      "createdAt": "<createdAt>"
    },
    "name": "validate_research_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
sourcesYes
dishNameYes
createdAtYes
confidenceYes
uncertaintyYes
extractedFactsYes

Output Schema

NameRequiredDescriptionDefault
issuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description usefully adds that failures surface as a returned list of issues rather than an exception, and that input is the build_research_record output. It does not state whether any part of the record is normalized or rejected, nor any auth or size constraints.

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?

Three short sentences, front-loaded with purpose, then usage, then input provenance, with no filler or repetition.

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?

The tool is structurally self-describing (required fields, enums, nested shapes) and an output schema exists, so return details are covered elsewhere. However, for a validator with a deeply nested input, the description omits what constitutes an issue and how severe or actionable the returned list is, leaving a meaningful gap.

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% across 7 required parameters, several nested, and the description only loosely gestures at two of them ('source metadata' and 'extracted facts'). Fields like query, dishName, uncertainty, confidence, and createdAt get no explanation anywhere, so the description does not compensate for the coverage gap beyond pointing at the producing tool.

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?

States a specific verb and resource: 'Validate that a typed research record has source metadata and extracted facts,' plus the return shape ('validation result with a list of issues'). It distinguishes the resource (research record) from the sibling validate_recipe_output only implicitly, so it is clear but not fully differentiated.

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?

Explicitly says when to use it ('checking a research record before passing it to dossier-building tools') and where the input comes from ('Pass the record from build_research_record output'), naming the producer sibling. It does not say when NOT to use it or what to do if validation fails.

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