Skip to main content
Glama
SVerITG

Metis

by SVerITG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Metis — Create Project Full

create_project_full

Creates a fully integrated Metis project by recording its database entry, generating CLAUDE.md, and linking Claude Desktop, so installers and dashboards can set up projects consistently.

Instructions

Create a project with full Metis integration: DB record, CLAUDE.md, Claude Desktop.

This is the unified project creation tool used by all installers and the dashboard.

Args:
    title:        Project name.
    folder_path:  Absolute path to the project folder on disk.
    category:     User-defined category (e.g. 'Article', 'Grant', 'Teaching').
    description:  What this project is about. If empty and scan_type != 'none',
                  auto-detected from folder.
    scan_type:    'names' | 'content' | 'none' — how to infer description from folder.
    link_claude_desktop_auto: Write project to Claude Desktop config automatically.

Input Schema

NameRequiredDescriptionDefault
titleYes
categoryNo
scan_typeNonames
descriptionNo
folder_pathNo
link_claude_desktop_autoNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided, so description must fully disclose behavioral traits. It does not mention idempotency, error handling on existing project, permissions, or side effects beyond creation. The listing of integrations is informative but insufficient for safe invocation.

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?

Very concise: two short sentences plus a clean arg list. All content adds value without redundancy. Front-loaded purpose.

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?

Output schema exists, so return value is covered. However, with 6 parameters and no behavioral context (e.g., overwrite behavior, folder requirements), the description lacks completeness for a tool of this complexity.

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?

Schema descriptions are absent (0% coverage), so the description carries the full burden. Each parameter has a concise explanation, with useful details like auto-detection for description and scan_type options. Title explanation is minimal but acceptable.

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 it creates a project with full Metis integration including DB record, CLAUDE.md, and Claude Desktop. It also notes it is the unified tool used by installers and dashboard, but does not explicitly differentiate from sibling 'create_project'.

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?

Describes intended use as the unified project creation tool, implying it is the standard path. However, no explicit guidance on when to use alternatives (e.g., simpler create_project) or when not to use this tool.

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