Skip to main content
Glama

query_research_timeline

Show the evolution of research beliefs over time for a given entity. Retrieve dated claims to trace how understanding has changed, optionally including superseded claims for the full reasoning chain.

Instructions

Query the temporal evolution of research beliefs.

Returns all claims for an entity ordered by date, showing how thinking
evolved. Superseded claims (older beliefs you updated) are hidden by default
but can be shown to trace the full reasoning chain.

Args:
    entity: Filter by entity name (partial match). Leave empty to see all
        recent entries across all entities.
    since_date: ISO date string (YYYY-MM-DD). Only show entries on or after
        this date. Leave empty for all time.
    show_superseded: If True, include claims that have been replaced by newer
        ones. Default False — shows only the current belief for each topic.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entityNo
since_dateNo
show_supersededNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

The description discloses key behaviors: returns claims ordered by date, hides superseded by default but can include them. No annotations exist, so the description carries the transparency burden adequately.

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?

The description is well-structured with a clear purpose sentence followed by parameter details. It is concise but covers necessary information without verbosity.

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?

Given the tool has an output schema and only three parameters, the description provides sufficient context about returns and options. It explains the temporal evolution and supersedence logic, making it complete for agent use.

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?

No schema descriptions for parameters (0% coverage), but the description explains each parameter thoroughly: entity (partial match, leave empty), since_date (ISO format, on/after), show_superseded (boolean, default False). This fully compensates for missing schema info.

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 queries the temporal evolution of research beliefs, with a specific verb and resource. It distinguishes itself from sibling tools by focusing on timeline ordering and superseded claims.

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 explains the tool returns claims ordered by date and mentions parameter usage. It does not explicitly state when not to use it or alternatives, but the context is clear enough for selection.

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_PH'

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