Skip to main content
Glama

Metis — Record Research Finding

record_research_finding

Record timestamped research beliefs and findings about an entity, link evidence, set confidence, and supersede prior claims to preserve a traceable reasoning timeline across sessions.

Instructions

Record a timestamped research belief or finding about an entity.

Use this whenever you reach a conclusion, update a previous belief, or
encounter evidence that changes your view. The timeline preserves the full
chain of reasoning across sessions.

Args:
    entity: What this claim is about. Use a consistent name across sessions
        (e.g. "RDT sensitivity in low-burden areas", "Disease X elimination study",
        "REDCap form completion rate").
    claim: Your current belief or finding in 1-3 sentences.
    evidence: What supports this claim — paper citation, data result, meeting
        discussion. Brief reference is enough.
    confidence: "low", "medium", or "high".
    source_type: "session", "paper", "meeting", "data_analysis", "literature_review".
    source_ref: Specific reference — DOI, file path, meeting date.
    supersedes_id: If this replaces a previous claim, pass that claim's id.
        Set to 0 if this is a new claim with no predecessor.

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": {
      "entity": "<entity>",
      "claim": "<claim>"
    },
    "name": "record_research_finding"
  }
}

Input Schema

NameRequiredDescriptionDefault
claimYes
entityYes
evidenceNo
confidenceNomedium
source_refNo
source_typeNosession
supersedes_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden but does disclose meaningful behavior: entries are timestamped, the timeline preserves a reasoning chain across sessions, and supersedes_id supersedes a prior claim. It is silent on whether records are editable or deletable, how conflicts between competing claims are resolved, and whether anything else is mutated.

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

Conciseness4/5

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

Purpose is front-loaded in the first sentence, followed by usage guidance and a compact Args block; each line carries information. The only redundancy is a slight overlap between the opening sentence and the first usage sentence.

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?

Output schema exists, so return values need no explanation, and all seven parameters are covered with formats and defaults. It could go further by pointing to the read-side siblings (query_research_timeline, list_research_entities) so an agent knows how the recorded chain is later retrieved.

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

Parameters5/5

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

Schema coverage is 0% and there are 7 parameters, yet the description documents every one: entity naming conventions with concrete examples, claim length guidance, evidence content, the allowed confidence values, the allowed source_type values (which the schema does not supply as an enum), source_ref formats, and supersedes_id=0 semantics for new claims. This fully compensates for the undocumented schema.

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 ('Record a timestamped research belief or finding about an entity') plus the timeline framing that distinguishes it from plain memory writes. It does not explicitly name the closest siblings (record_decision, remember, store_semantic_memory, record_data_story), so an agent must infer the boundary from context.

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?

'Use this whenever you reach a conclusion, update a previous belief, or encounter evidence that changes your view' gives clear triggering conditions, and the supersedes_id guidance covers the update case. It offers no explicit exclusions or named alternatives for when a decision, generic memory, or session event is the better record type.

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