Skip to main content
Glama
Sign In
things-mcp

things-mcp

by than
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

add_project

Create a new project and optionally populate it with to-dos, tags, notes, and deadlines.

Instructions

Create a project, optionally pre-filled with to-dos.

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": "add_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNo
tagsNo
whenNo
notesNo
titleYes
todosNo
deadlineNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It merely states 'Create' but does not disclose behavioral traits such as whether it can overwrite existing projects, authentication needs, or side effects. Significant gaps remain.

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 sentence with no waste, but it is too short to be effective for a tool with 7 parameters. It could be expanded to cover more details without losing conciseness.

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?

The tool has 7 parameters, no output schema, and no annotations. The description only mentions creation and optional to-dos, ignoring return values, side effects, parameter details, and prerequisites. It is severely incomplete.

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%, but the description only clarifies the 'todos' parameter (pre-filled). Other parameters like area, tags, when, notes, and deadline are left unexplained, adding minimal semantic value beyond their names.

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 uses a specific verb ('Create') and resource ('project'), and adds the optional pre-fill with to-dos, which distinguishes it from siblings like update_project and add_todo. However, it could be more explicit about what constitutes a project.

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, when not to use, or comparisons to siblings like update_project or add_todo.

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