Skip to main content
Glama
deeptrue MCP

deeptrue MCP

Official
by deeptrue-ag

Finish fielding

finish_fielding
Destructive

Finish a data-collecting project by providing its project ID and confirm=true, closing fielding once data collection is complete.

Instructions

Finish a project that is collecting data. 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": "finish_fielding"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.4/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds a genuine operational constraint not visible in structured data (confirm must be true), but it does not say what "finishing" actually does to the project or its collected data, nor whether it is reversible.

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 with no filler, and the operational precondition plus the confirm gate are front-loaded where an agent will see them. It is terse rather than padded, which is the right trade-off for a simple 3-parameter tool.

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 destructive lifecycle mutation with no output schema, the definition covers the gate but omits the consequences: what state the project ends in, what happens to responses already collected, and what the tool returns. Adequate to invoke correctly, thin on outcome expectations.

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 33%; the organization parameter is documented in-schema, but confirm and project_id are not. The description compensates partially by stating confirm=true is required even though the schema marks it optional, which is meaningful added semantics. project_id's meaning is left to inference.

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?

"Finish a project that is collecting data" gives a concrete verb (finish) and resource (project) plus a state precondition, so an agent knows what operation this performs. It stops short of differentiating itself from near-siblings such as archive_project or accept_project, which also act on a project's lifecycle.

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?

The phrase "project that is collecting data" implicitly scopes when this applies, and the confirm requirement signals a deliberate, gated action. However, there is no explicit guidance on when to choose this over archive_project, nor what happens to the already-collected data, so the agent must infer the alternative.

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