BuildBetter MCP Research

Use BuildBetter domain tools before GraphQL helpers. Use run-query only when discovery confirms that no domain tool expresses the request.

Read references/mcp-tool-map.md when exact tool names, arguments, pagination rules, or multi-source examples are needed.

This skill adds reusable routing and evidence discipline over the MCP's general-purpose read tools. It does not replace MCP behavior or encode a tenant's taxonomy. Feature-scoped and mutating workflows route to dedicated skills when those skills and their tools are available.

Research Workflow

1. Translate the question into a retrieval plan: evidence source, organization-specific metadata, filters, time range, and the minimum detail needed to answer.
2. Discover before guessing. List configured signal types, tags, properties, project types, or GraphQL fields when the request depends on them.
3. Choose the narrowest domain tool. Use aggregate tools for totals or distributions, search/list tools for candidate discovery, and detail tools for exact evidence.
4. Start with a stable page of 20 to 40 results unless the user requests an export. Keep filters unchanged while paging.
5. Inspect returned IDs, dates, boundaries, people, companies, source kinds, types, and truncation metadata before synthesizing.
6. Deepen only the best candidates with call, transcript, document, knowledge-page, or project detail tools.
7. Answer with the scope searched, evidence identifiers, findings, and material coverage limitations. Never imply that unqueried sources were searched.

Routing