Skip to main content
Glama
AdiRatnam

AI Research Agent

by AdiRatnam

render_dashboard

Create a dashboard for a research report using title, summary, key points, and references, and output the URL.

Instructions

Use Prefab to display the report dashboard in the background and return the URL.

Args:
    title: The research title.
    summary: The summary of the research.
    key_points: List of key points.
    references: List of references URLs.
    file_name: The saved file name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
summaryYes
file_nameYes
key_pointsYes
referencesYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, and the description only mentions 'display in the background and return the URL' without disclosing side effects, permissions, or limitations.

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?

The description is concise: one sentence for purpose followed by a parameter list. No unnecessary words.

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?

The tool has 5 required parameters and an output schema; the description covers purpose and all parameters adequately for a straightforward render tool.

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?

Despite 0% schema description coverage, the description's docstring provides brief explanations for each parameter (title, summary, key_points, references, file_name), adding context beyond the schema types.

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 renders a dashboard using Prefab and returns a URL. It distinguishes from siblings (research_topic, manage_report) by focusing on display.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when you have report data to visualize but provides no explicit when-to-use or when-not-to-use guidance relative to siblings.

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/AdiRatnam/AI-Research-Agent'

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