Skip to main content
Glama
deeptrue MCP

deeptrue MCP

Official
by deeptrue-ag

Create project

create_project

Creates a project in the active organization to start a new research brief, using a required name plus optional briefing answers and confirmation.

Instructions

Create a project in the active organization. Use when starting a new research brief. Requires mcp:write.

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

Input Schema

NameRequiredDescriptionDefault
jsonNoInitial briefing answers JSON
nameYesProject name
confirmNoMust be true to create
organizationNoOrganization domain/slug for this call only. It does not persist. HTTP clients can also send X-DeepTrue-Org. Stdio defaults to DEEPTRUE_ORG.
product_slugNoProduct slug when known

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the write-but-non-destructive profile is known. The description adds genuinely useful authorization context ("Requires mcp:write") that annotations don't carry, but says nothing about duplicate-name behavior, what the call returns, or how the initial briefing JSON interacts with submit_briefing_answers.

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?

Three short, front-loaded sentences with no filler: purpose, usage trigger, then auth requirement. Sizing is appropriate for a simple creation tool; no sentence is wasted.

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?

For a five-parameter create tool with full schema coverage and no output schema, the definition covers purpose, trigger, and auth. The gaps (return value, duplicate handling, briefing payload semantics) are real but minor given the schema richness.

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?

Schema description coverage is 100%, so per-call organization override, the confirm gate, and product_slug are already documented in the schema and the description need only match that baseline. It does add the "active organization" framing, but that slightly muddies the schema's note that the organization parameter is call-scoped and does not persist, and it adds nothing about the nested json briefing object.

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?

States a specific verb and resource ("Create a project") plus a scoping qualifier ("in the active organization"), which separates it from sibling mutations like update_project or archive_project. It stops short of naming an explicit alternative, but the action is unambiguous.

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?

"Use when starting a new research brief" gives a clear triggering context, which is more than nothing. However there are no exclusions, no prerequisites beyond the auth note, and no routing guidance versus siblings such as submit_briefing_answers or list_projects.

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