Skip to main content
Glama
SVerITG

Metis

by SVerITG
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

create_project

Create a permanent project record in Metis to track research conversations and enable task linking and memory search.

Instructions

Register a new project in the Metis platform.

Called when a researcher confirms they want a Claude conversation or project
tracked permanently in Metis. Creates the project record in the DB so it
appears in the Work tab and is available for task linking and memory search.

Args:
    title: Human-readable project name, e.g. "Statistics Course".
    description: What this project is about (one sentence).
    domain: Research domain, e.g. "education", "epidemiology". Optional.
    source: Origin — "claude_project" (default), "claude_cowork", or "manual".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
descriptionNo
domainNo
sourceNoclaude_project

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the action (creating a DB record) and consequences (appears in Work tab, available for linking). However, it omits details like duplicate handling, error conditions, or required permissions, which would enrich transparency.

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 very concise: a short introductory paragraph followed by clear bullet points for parameters. Every sentence adds value without redundancy. The structure is front-loaded with purpose, making it easy to scan.

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 complexity (4 parameters, 1 required) and presence of an output schema, the description adequately covers the tool's effect (DB creation, Work tab visibility). It lacks mention of return values or edge cases, but the output schema presumably fills that gap. Slightly incomplete for a create tool expecting an ID back.

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?

The description includes detailed docstring-style explanations for each parameter (title, description, domain, source), including examples and default values. Since the input schema has 0% description coverage, the description fully compensates by adding meaning beyond property 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 clearly states the tool registers a new project in the Metis platform, specifies the triggering condition (researcher confirming permanent tracking), and explains the effect (DB record creation, appearing in Work tab). It distinguishes itself from siblings like 'create_project_full' by being the basic creation tool.

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 provides explicit context for when to use this tool ('Called when a researcher confirms they want... tracked permanently'). However, it does not mention when not to use it or contrast with alternatives such as 'create_project_full', leaving the agent to infer exclusivity.

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'

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