Skip to main content
Glama
Sign In
things-mcp

things-mcp

by than
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

update_project

Modify a project's title, tags, notes, deadline, completion, or cancellation status by its ID.

Instructions

Update an existing project by id (requires Things URLs enabled).

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

Input Schema

NameRequiredDescriptionDefault
idYes
tagsNo
whenNo
notesNo
titleNo
canceledNo
deadlineNo
completedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

No annotations provided, so description must disclose behavior. Only says 'update', implying mutation, but does not mention side effects, error handling (e.g., missing id), or authorization needs.

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

Conciseness2/5

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

Extremely short, but lacks essential information. Under-specification outweighs brevity; fails to provide value.

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?

With 8 parameters, no output schema, and no annotations, the description leaves most behavioral and parameter details unspecified, making the tool hard to use correctly.

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

Parameters1/5

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

Schema coverage is 0% and description does not explain any parameter. The agent cannot infer the meaning of tags, when, notes, etc., 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 states 'Update an existing project by id', which clearly identifies the verb and resource. It distinguishes from siblings like add_project (creation) but includes an unclear prerequisite 'requires Things URLs enabled'.

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 on when to use this tool versus alternatives like add_project for creation or cancel_todo for tasks. Missing context on appropriate scenarios.

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