Skip to main content
Glama
deeptrue MCP

deeptrue MCP

Official
by deeptrue-ag

Submit briefing answers

submit_briefing_answers

Submit briefing answers by patching a project's JSON file before accepting the project; requires confirm=true to proceed.

Instructions

PATCH project.json with briefing answers. Use before accept_project. 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>",
      "answers": "<answers>"
    },
    "name": "submit_briefing_answers"
  }
}

Input Schema

NameRequiredDescriptionDefault
answersYesBriefing answers object stored on project.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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and openWorldHint=false, so the mutating, closed-world nature is covered. The description adds the non-obvious confirm=true gate, which is valuable, but says nothing about whether existing answers are merged or replaced, whether the call is idempotent, or what happens on rejection.

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

Conciseness5/5

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

Two short sentences, purpose front-loaded, with the workflow constraint and the confirm precondition following. No filler or restatement of the title.

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 4-parameter, nested-object mutation with no output schema, the description covers purpose and ordering but leaves the answers payload semantics (merge vs replace), error behavior, and org scoping unaddressed. Adequate to invoke, thin for invoking correctly on repeat or partial-submission cases.

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 coverage is 50%; the answers object is documented in the schema, and the description usefully flags that confirm=true is mandatory even though the schema's required list does not include it. However, project_id and organization (including the org-scoping/header behavior) get no coverage in the description.

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 concrete verb and target ("PATCH project.json with briefing answers"), which tells an agent it writes briefing data onto the project record. It also positions the tool in a workflow ("before accept_project"), distinguishing it from accept_project itself, though it does not differentiate against get_briefing or update_project.

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?

"Use before accept_project" gives explicit sequencing guidance that an agent can act on, and "Requires confirm=true" is a stated precondition. There is no when-not guidance (e.g., what to do if briefing was already submitted) and no mention of an alternative tool for reading existing answers.

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