Skip to main content
Glama

validate-headings

Check if specific headings already exist in a Things 3 project by comparing against expected heading names to verify project structure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_uuidYesUUID of the project to inspect
expected_headingsYesHeading names that should already exist in the project

Implementation Reference

  • The handler for the "validate-headings" tool. It takes a project UUID and a list of expected headings, compares them with the headings existing in the Things database, and returns a status indicating whether all required headings are present.
    server.tool(
      "validate-headings",
      {
        project_uuid: z.string().describe("UUID of the project to inspect"),
        expected_headings: z
          .array(z.string())
          .min(1)
          .describe("Heading names that should already exist in the project"),
      },
      async ({ project_uuid, expected_headings }) => {
        const result = await withDatabase((db) => {
          const tasks = getAllTasks(db);
          const project = tasks.find(
            (task) => task.type === "project" && task.id === project_uuid && !task.trashed
          );
          const existingHeadings = tasks
            .filter(
              (task) =>
                task.type === "heading" &&
                task.projectId === project_uuid &&
                !task.trashed
            )
            .map((task) => task.title);
    
          return {
            projectTitle: project?.title ?? null,
            existingHeadings,
          };
        });
    
        const existingByNormalized = new Map(
          result.existingHeadings.map((heading) => [normalizeHeadingName(heading), heading])
        );
        const expected = uniqueHeadingNames(expected_headings);
        const presentHeadings = expected
          .filter((heading) => existingByNormalized.has(normalizeHeadingName(heading)))
          .map((heading) => existingByNormalized.get(normalizeHeadingName(heading)) ?? heading);
        const missingHeadings = expected.filter(
          (heading) => !existingByNormalized.has(normalizeHeadingName(heading))
        );
    
        return buildTextResponse("Validated project headings", {
          projectUuid: project_uuid,
          projectTitle: result.projectTitle,
          expectedHeadings: expected,
          existingHeadings: result.existingHeadings,
          presentHeadings,
          missingHeadings,
          isReady: missingHeadings.length === 0,
          userInstruction:
            missingHeadings.length === 0
              ? "All required headings exist. You can continue creating or moving tasks into those headings."
              : buildHeadingCreationPrompt({
                  projectTitle: result.projectTitle ?? undefined,
                  suggestedHeadings: expected,
                  missingHeadings,
                }),
        });
      }
    );
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/soycanopa/SupaThings-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server