Skip to main content
Glama
Sign In
research-hub

research-hub

by WenyuChiou
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

import_folder_tool

Ingest non-DOI files from a local folder into your research workspace as document notes.

Instructions

Walk a local folder and ingest non-DOI files as document notes.

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": {
      "folder": "<folder>",
      "cluster_slug": "<cluster_slug>"
    },
    "name": "import_folder_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
folderYes
cluster_slugYes
dry_runNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/5.0
Behavior2/5

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

The description lacks behavioral details beyond the core action. It does not disclose side effects (e.g., file creation, metadata updates), permissions needed, error handling, or any constraints. Without annotations, the agent has insufficient behavioral context.

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

Conciseness2/5

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

The description is extremely brief (one sentence) but fails to convey essential information. It is underspecified rather than concise, lacking detail that is necessary for effective tool selection and invocation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of parameter descriptions, usage guidance, and behavioral transparency, the description is severely incomplete. The existence of an output schema does not compensate for the lack of input and usage context.

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

Parameters1/5

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

The description provides no information about the three parameters ('folder', 'cluster_slug', 'dry_run'). With 0% schema description coverage, the agent cannot infer the meaning, format, or purpose of these inputs beyond their names and 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 states a specific verb 'walk and ingest' targeting a resource 'local folder' and 'non-DOI files', clearly indicating what the tool does. It differentiates from siblings by implying it handles folder ingestion, which is distinct from other sibling tools like 'add_paper' or 'search_papers'.

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 guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or comparison to other import or ingestion tools among the siblings.

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