Skip to main content
Glama
deeptrue MCP

deeptrue MCP

Official
by deeptrue-ag

List projects

list_projects
Read-only

Retrieve DeepTrue projects in the active organization to inventory work and scan statuses, with optional search, pagination, and a per-call organization override.

Instructions

List DeepTrue projects in the active organization. Use for inventory and status scans.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
searchNo
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.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the useful constraint that results are scoped to the active organization, but says nothing about pagination behavior, result ordering, or how the organization context is resolved (the schema mentions X-DeepTrue-Org and DEEPTRUE_ORG, but the description does not).

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 the resource identification front-loaded and no filler. Nothing important is buried, though the second sentence is vague enough that it earns its place only marginally.

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 read-only list tool with no output schema, the definition covers what is listed and where, but omits how results are returned (shape, ordering, pagination) and leaves three of four parameters entirely unexplained given the 25% schema coverage.

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 description coverage is only 25%: only the organization parameter is documented in the schema, while limit, offset, and search carry no explanations anywhere. The description adds no meaning for any parameter, so an agent must guess that search is a name filter or that limit/offset drive pagination.

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 opens with a specific verb and resource ("List DeepTrue projects") and scopes it to the active organization, which is meaningful for a tenant-aware API. It does not distinguish itself from the close sibling list_panel_projects, so an agent cannot be fully sure which list to use from this text alone.

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?

"Use for inventory and status scans" implies a browse/enumerate context but gives no explicit when-not guidance, no prerequisites, and no reference to alternatives such as list_panel_projects. Adequate but thin.

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