Skip to main content
Glama

record_research_finding

Record timestamped research findings to preserve your reasoning chain across sessions. Capture claims, evidence, and confidence to track knowledge evolution.

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",
        "DHIS2 tracker performance").
    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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entityYes
claimYes
evidenceNo
confidenceNomedium
source_typeNosession
source_refNo
supersedes_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description carries full burden. Mentions timestamping and timeline preservation but does not disclose permissions, storage limits, or whether records are immutable. Adequate but not thorough.

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?

Well-structured with a lead sentence, usage context, and parameter documentation. Slightly lengthy but all content is valuable; front-loaded with purpose.

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?

Covers all 7 parameters, with output schema present to handle return values. Missing edge-case details like behavior of supersedes_id=0 but overall complete for a recording tool.

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 has 0% description coverage, but the description includes a detailed Args section explaining each parameter's purpose, format, and defaults, adding significant meaning beyond the raw 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?

Description clearly states 'Record a timestamped research belief or finding about an entity.' It uses specific verb and resource, but does not explicitly distinguish from similar sibling tools like add_memory_entry or capture_observation.

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?

Provides explicit when-to-use guidance: 'Use this whenever you reach a conclusion, update a previous belief, or encounter evidence that changes your view.' No when-not-to-use or alternatives mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SVerITG/Metis'

If you have feedback or need assistance with the MCP directory API, please join our Discord server