Skip to main content
Glama
deeptrue MCP

deeptrue MCP

Official
by deeptrue-ag

Update project

update_project

Patch project fields such as name or JSON, including briefing answer edits before acceptance, to correct or update project data without replacing the full record.

Instructions

PATCH project fields (name/json/etc). Use for briefing answer edits before accept.

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

Input Schema

NameRequiredDescriptionDefault
patchYesPartial project payload
confirmNo
project_idYes
organizationNoOrganization domain/slug for this call only. It does not persist. HTTP clients can also send X-DeepTrue-Org. Stdio defaults to DEEPTRUE_ORG.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare a non-read-only, closed-world mutation, and the description adds workflow context (edits happen before accept). It says nothing about the 'confirm' flag in the schema, whether partial patches merge or replace, or which fields are mutable, leaving meaningful behavioral gaps.

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?

Two short sentences, front-loaded with the verb and resource, with no filler. It is arguably too terse rather than too long, but nothing is wasted.

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?

For a mutation tool with a nested free-form patch object, no output schema, and an undocumented confirmation parameter, the description leaves too much implicit: merge behavior, mutable field surface, and confirm semantics are all missing.

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 coverage is only 50%: patch and organization are documented, but project_id and especially confirm are undocumented anywhere. The description's 'name/json/etc' only loosely sketches patch contents and does nothing to explain confirm or the merge semantics of a partial payload.

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 names a specific verb (PATCH, i.e. partial update) and resource (project fields), which separates it from siblings such as accept_project or update_survey_structure. The field list 'name/json/etc' is vague but the operation itself 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?

It gives one concrete scenario ('briefing answer edits before accept') and implies sequencing relative to accept_project, which is genuinely useful. However, it offers no exclusions or guidance for the many other project edits an agent might want to make, so the agent must infer the rest.

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