Skip to main content
Glama

stitch_find

Lists Stitch projects, screens, or design systems by resource type and returns matching items, count, and pagination details to support filtering and browsing.

Instructions

Lists Stitch resources of a given type (projects, screens, design-systems). Mirrors 'stitch find '. Returns items list, count, and pagination info.

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": {
      "resource": "<resource>"
    },
    "name": "stitch_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of items to return
filterNoAIP-160 filter expression
projectNoStitch Canvas project ID
criteriaNoResource-specific filter criteria
resourceYesResource type to list
workspaceNoWorkspace ID override

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. “Lists” suggests a read operation, and the disclosure of an items list, count, and pagination information is useful, but side-effect safety, access requirements, default limits, pagination behavior, and error or filtering semantics remain unspecified.

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

Conciseness5/5

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

The description is compact and front-loads the operation and supported resource types. The CLI equivalence and returned information each add distinct value without unnecessary wording.

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

Completeness3/5

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

It is adequate for a basic invocation because the required resource type and high-level result are clear, while the schema covers parameter basics. For a six-parameter tool with nested criteria, no annotations, and no output schema, however, it leaves filter interactions, pagination details, and operational prerequisites insufficiently explained.

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 structured schema already documents all six parameters. Mirroring 'stitch find <resource>' adds modest context for the resource argument, but the description does not clarify interactions between filter and criteria, when project applies, or how workspace override and limit behave.

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 clearly states the verb and resource scope: listing Stitch projects, screens, and design-systems. It also gives the equivalent CLI operation, but does not explicitly distinguish this tool from siblings such as stitch_resource or other listing tools.

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

Usage Guidelines3/5

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

Usage is implied for agents that need to enumerate one of the named Stitch resource types. There is no explicit guidance on when to prefer this tool over stitch_resource, brand_list, or a direct resource lookup, nor any stated exclusions or prerequisites.

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