Amazing Marvin MCP

Overview Schema Source Related Servers Discussions Admin

create_project

Create a new project in Amazing Marvin by specifying a title and optional project type. Structure your task management with defined projects.

Instructions

Create a new project in Amazing Marvin

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": {
      "title": "<title>"
    },
    "name": "create_project"
  }
}

Input Schema

Name	Required	Default
`title`	Yes
`project_type`	No	project
`debug`	No

Output Schema

Name	Required	Description	Default
`data`	Yes
`metadata`	Yes	Metadata about the data itself
`summary`	Yes	Human-readable insights
`debug`	Yes
`success`	Yes
`api_version`	No		current
`response_version`	No		1.0

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Jun 10, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states 'create a new project' without disclosing side effects, permissions, or error handling. Minimal transparency.

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

Conciseness3/5

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

The description is a single concise sentence, but it is too brief for a tool with 3 parameters and no schema descriptions. It sacrifices helpful detail for brevity.

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

Completeness2/5

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

Given the lack of annotations and schema descriptions, the description is incomplete. It does not cover parameter usage, return values, or behavioral context for a 3-parameter tool.

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

Parameters2/5

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

Schema description coverage is 0%, and the description adds no meaning to parameters. The 'project_type' and 'debug' fields are not explained, leaving the agent without guidance on valid values or effects.

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 'Create a new project in Amazing Marvin', specifying the verb and resource. However, it does not differentiate from the sibling 'create_project_with_tasks', which could cause confusion.

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 like 'create_project_with_tasks'. The description only implies its basic function without any exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.