Skip to main content
Glama

json

Create new Things 3 projects with headings and nested to-dos by processing JSON payloads in one operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
auth-tokenNo
dataYesRaw Things JSON payload. Prefer this tool for creating a brand-new project with headings and nested to-dos in one operation.
revealNoReveal the first created item in Things after processing the JSON payload

Implementation Reference

  • The 'json' tool handler, which processes a raw JSON payload for creating structured items in Things 3, including project-with-headings structures.
      "json",
      {
        "auth-token": z.string().optional(),
        data: z.string().describe("Raw Things JSON payload. Prefer this tool for creating a brand-new project with headings and nested to-dos in one operation."),
        reveal: z.boolean().optional().describe("Reveal the first created item in Things after processing the JSON payload"),
      },
      async (params) => {
        const enriched = await enrichWriteParams("json", { ...params });
        const url = await openThingsURL("json", buildURLParams(enriched));
        return buildTextResponse("Processed JSON payload in Things", {
          url,
          guidance:
            "Use this tool for structured creation flows, especially brand-new projects that need headings. Do not rely on it to add new headings to an existing project unless the payload is creating the project itself.",
        });
      }
    );
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