Skip to main content
Glama
AdiRatnam

AI Research Agent

by AdiRatnam

manage_report

Create, read, update, or delete report files in the reports directory. Specify an action and filename to manage report content.

Instructions

Perform CRUD operations on reports.

Args:
    action: One of 'create', 'read', 'update', 'delete'.
    filename: The name of the file in the reports/ directory.
    content: The text content for create/update.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes
contentNo
filenameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are present. The description indicates CRUD operations but does not disclose behavioral traits such as file system constraints, idempotency, side effects, or permission requirements. For a mutation-capable tool, this is insufficient.

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 concise, front-loaded with the purpose, and uses a structured Args block. Every sentence provides necessary information without redundancy.

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?

Given the output schema exists, the description does not need to cover return values. It adequately lists the parameters and their roles. However, it fails to provide behavioral context or usage boundaries, leaving gaps for an AI agent.

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

Parameters3/5

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

The schema has 0% description coverage, so the description must compensate. It explains that 'action' is one of 'create', 'read', 'update', 'delete', 'filename' is a file in 'reports/' directory, and 'content' is for create/update. This adds meaning beyond the bare schema but lacks detail on constraints like valid characters or path formats.

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?

The description clearly states 'Perform CRUD operations on reports' and lists the arguments. This makes the primary purpose evident, and its distinction from siblings like 'research_topic' and 'render_dashboard' is clear.

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

Usage Guidelines2/5

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

No explicit guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or scenarios where a sibling tool would be more appropriate.

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