Skip to main content
Glama

stitch_resource

Read, edit, or delete one design resource, such as a project, screen, or design system, or get its canonical canvas URL.

Instructions

Read, edit, or delete one Stitch resource, or print its canonical canvas URL. Select action: get, edit, delete, or url.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "stitch_resource"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoResource ID (omit only for status)
bodyNoFields to update for edit
actionYesStitch resource operation
projectNoStitch Canvas project ID
resourceNoResource type (get/edit/delete; url uses project|screen)
workspaceNoWorkspace ID override

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden, and it does not warn that "delete" is irreversible or that "edit" may replace rather than merge fields. It gives no indication of permission requirements, failure modes, or what a get/url call returns, leaving the destructive and mutating paths under-described.

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 tight sentences with the operations front-loaded and no filler. The second sentence partially duplicates the action enum already present in the schema, which is minor waste but not damaging.

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

Completeness2/5

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

For a six-parameter, multi-mode tool with a nested body object, no output schema, and no annotations, the description is too thin. It never explains what goes in body for edit, what get returns, or how url differs when resource is project versus screen.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all six parameters including the action and resource enums and the "omit only for status" rule for id. The description adds essentially nothing beyond the schema and even omits the status case that the schema references.

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 states a concrete resource ("one Stitch resource") and enumerates the four operations it performs, plus an unusual extra capability ("print its canonical canvas URL"). That distinguishes it reasonably from create/find/generate siblings, though the overlap between "get" and a sibling like stitch_find is never resolved.

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

Usage Guidelines2/5

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

The only guidance is "Select action: get, edit, delete, or url," which is a restatement of the action enum rather than when-to-use guidance. There is no statement of prerequisites, no when-not-to-use, and no pointer to alternatives for fetching or searching resources.

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