Skip to main content
Glama
deeptrue MCP

deeptrue MCP

Official
by deeptrue-ag

Start fielding

start_fielding

Begins data collection for an accepted project and requires explicit confirmation before proceeding.

Instructions

Begin data collection (collect) for an accepted 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>"
    },
    "name": "start_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

A3.5/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 agent knows this is a state-changing, closed-world operation; the description adds the confirmation guard ('Requires confirm=true'), which is genuinely useful behavioral context. It stops short of saying what the project's status becomes, whether collection can later be halted, or what happens if the project was never accepted, all of which matter for a mutation.

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, no filler, with the action and the confirmation requirement front-loaded. Every clause earns its place.

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?

There is no output schema, so the description need not explain return values, and annotations cover the safety profile. Still, for a state-mutating lifecycle tool in a family with accept/finish siblings, it leaves out the resulting state change, error conditions for non-accepted projects, and the stopping counterpart.

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 description coverage is only 33%, with project_id and confirm undocumented in the schema, so the description carries part of the burden: it clarifies that confirm must be true and constrains project_id to an accepted project. It does not explain that project_id accepts either a string or number identifier, nor what value confirm should take if omitted.

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 uses a specific verb phrase ('Begin data collection') tied to a specific resource ('an accepted project') and even names the underlying action ('collect'), so the agent knows exactly what operation this performs. It implies the inverse of the sibling 'finish_fielding' through the start/finish framing, but does not name it explicitly.

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?

'For an accepted project' is a real precondition that tells the agent this is not the tool for draft or archived projects, and 'Requires confirm=true' is a hard invocation requirement. However, there is no explicit when-not guidance, no mention of 'accept_project' as the prerequisite step, and no pointer to 'finish_fielding' for stopping collection.

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