Skip to main content
Glama
deeptrue MCP

deeptrue MCP

Official
by deeptrue-ag

Accept project

accept_project

Accept a project offer and start its survey collection. Use this to move a briefed project into the collect stage; requires a project ID and confirm=true to proceed.

Instructions

Accept a project offer and spawn the survey. Sequence: briefing → accept → collect. Requires confirm=true.

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

Input Schema

NameRequiredDescriptionDefault
answersNoOptional briefing answers override (json)
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.
product_slugNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds the important behavioral fact that this call spawns a survey, i.e. it creates new downstream resources, and that confirm=true is mandatory as a safety gate. It does not say whether the accept is reversible or what happens to an already-accepted project, but the side-effect disclosure is substantive.

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 terse sentences, front-loaded with the action and consequence, followed by the workflow arrow notation. The word "collect" in the sequence is slightly opaque, but nothing is wasted.

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

Completeness3/5

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

For a mutating tool with five parameters, a nested object, no output schema, and low schema coverage, the description covers the confirm gate and the spawning consequence but leaves the identity semantics of project_id/product_slug and the effect of answers unresolved. Adequate as a minimum, but not complete enough for a state-changing call.

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?

With only 40% schema coverage, the description carries real weight: it explains that confirm must be true, which the schema leaves as a bare boolean. However, project_id (the sole required parameter) and product_slug remain unexplained, and the nested answers override object is only vaguely covered by its schema text.

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?

"Accept a project offer and spawn the survey" gives a specific verb plus the concrete side effect, which distinguishes it from read siblings like get_project and from start_fielding. It stops short of naming which sibling to use instead when a project is already accepted, so it doesn't reach full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The stated sequence "briefing → accept → collect" places the call in a workflow and implies the prerequisite that briefing must happen first, which is genuine when-to-use guidance. It does not state explicitly what happens if the sequence is skipped or which tool handles the post-accept step, so there are no explicit exclusions.

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