droid-mcp

droid_find

Read-only

Find Factory Droid sessions on this machine, grouped into workstreams and standalone sessions by repo; supports cursor paging and transcript search.

Instructions

Find the user's Factory Droid sessions on this machine, grouped into workstreams (orchestrator + agents) and standalone sessions by repo. Paged with cursor.

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": "droid_find"
  }
}

Input Schema

Name	Required	Description
`cwd`	No
`limit`	No
`query`	No	Match title, id prefix or cwd; with content=true, search transcripts instead
`scope`	No
`cursor`	No
`content`	No
`includeArchived`	No
`includeSubagents`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With readOnlyHint already declaring a safe read operation, the description adds the useful facts that results are grouped into workstreams and standalone sessions by repo, and that results are cursor-paged. It says nothing about default page size, ordering, or whether archived/subagent sessions are excluded by default, which an agent would need to know before paging.

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 sentences that front-load the core purpose, then the result grouping and pagination model. No filler or redundancy, though the paging note is tacked on rather than integrated.

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 no-required-parameter, read-only listing tool with no output schema, the description covers purpose, result shape, and paging adequately. It is not complete enough given four undocumented query options that materially change what is returned.

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 coverage is only 13% with 8 parameters, so the description must carry most of the parameter burden. It does convey the scope grouping and cursor pagination, but leaves content, includeArchived, includeSubagents, limit, and cwd entirely unexplained in both schema and prose.

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 names a specific verb and resource ('Find the user's Factory Droid sessions on this machine') and explains the result shape: workstreams (orchestrator + agents) and standalone sessions grouped by repo. That distinguishes it from droid_start/droid_send/droid_cancel, which are action tools rather than discovery tools. It stops short of explicitly naming a sibling to route against.

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 discovery framing implies when to use this tool, but there is no explicit guidance on when-not to use it, nor when to reach for a sibling like droid_result over droid_find. The scope enum choice (workstreams vs sessions vs all) is only obliquely hinted at by the grouping language.

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

Deploy Server