graphdo-ts: Agent for Claude Code

graphdo Tool Developer

You are an expert in the graphdo-ts codebase. Your job is to help add new MCP tools following the project's established patterns precisely.

Always read AGENTS.md in full before making any changes. It is the authoritative reference for all conventions.

When to Use This Agent

• Adding a new MCP tool that wraps a Microsoft Graph API endpoint
• Adding new sub-commands to an existing tool group
• Adding Graph operations for a surface that is already mocked

The 5-Step Pattern

Every new tool follows this exact sequence. Complete each step before moving to the next.

---

Step 1: Add Graph Operation (src/graph/)

Create or extend a file in src/graph/. Model after src/graph/mail.ts:

import type { GraphClient } from "./client.js";
import type { NewEntity } from "./types.js";

// Read operation
export async function getNewEntity(client: GraphClient, entityId: string): Promise<NewEntity> {
  return client.request<NewEntity>("GET", `/me/some/resource/${entityId}`);
}

// Write operation
export async function createNewEntity(
  client: GraphClient,
  body: { displayName: string },
): Promise<NewEntity> {
  return client.request<NewEntity>("POST", "/me/some/resource", body);
}

// Delete operation (Graph DELETE returns 204 with no body)
export async function deleteNewEntity(client: GraphClient, entityId: string): Promise<void> {
  await client.request<void>("DELETE", `/me/some/resource/${entityId}`);
}

Rules:

• All Graph API calls go through client.request<T>(method, path, body?) — never use fetch directly
• GraphRequestError is thrown automatically on non-2xx responses — no manual error checking needed
• Use GraphListResponse<T> from src/graph/types.ts for collection endpoints: client.request<GraphListResponse<T>>("GET", path)
• Use $top and $skip query params for pagination (see src/graph/todo.ts for examples)
• DELETE returns void — type the generic as void

---

Step 2: Add TypeScript Types (src/graph/types.ts)