Skip to main content
Glama

workflow

Read-only

Reads built-in figlens skill guides covering design-to-code builds, UI audits, image prep, search, scoped planning, and autonomous implementation, returning guidance only.

Instructions

Read built-in figlens skill guidance for this agent: build for design-to-code and project reuse, audit for comparing existing UI with a design and correcting confirmed differences, images for website asset preparation, search for an index, usages and following changes, plan for scoped implementation planning, planning-details for page/multi-page work or unresolved design dependencies, yolo for explicitly requested autonomous implementation and cleanup of what the run created. Returns the requested guide only; no design file, project read/write, implementation, verification or cleanup is performed. Ordinary design questions and exports can use the design tools directly.

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": {
      "topic": "<topic>"
    },
    "name": "workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesGuide to read: build, audit, images, search, plan, planning-details or yolo.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.11.3
    • changedInput schema / properties / topic / description
      Previous value: -"Guide to read: build, audit, images, plan, planning-details or yolo."New value: +"Guide to read: build, audit, images, search, plan, planning-details or yolo."
    • changedInput schema / properties / topic / enum
      Previous value: -[
      -  "build",
      -  "audit",
      -  "images",
      -  "plan",
      -  "planning-details",
      -  "yolo"
      -]New value: +[
      +  "build",
      +  "audit",
      +  "images",
      +  "search",
      +  "plan",
      +  "planning-details",
      +  "yolo"
      +]
  2. Changed2 schema fields changedv0.9.3
    • changedInput schema / properties / topic / description
      Previous value: -"Guide to read: build, images, plan, planning-details or yolo."New value: +"Guide to read: build, audit, images, plan, planning-details or yolo."
    • changedInput schema / properties / topic / enum
      Previous value: -[
      -  "build",
      -  "images",
      -  "plan",
      -  "planning-details",
      -  "yolo"
      -]New value: +[
      +  "build",
      +  "audit",
      +  "images",
      +  "plan",
      +  "planning-details",
      +  "yolo"
      +]
  3. Addedv0.7.2

TDQS

A4.7/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, and the description reinforces this by stating it "Returns the requested guide only; no design file, project read/write, implementation, verification or cleanup is performed" — valuable clarification that a topic like "yolo" does not itself execute implementation. It does not cover guide size or whether the returned guidance is meant to be acted on afterwards, so slightly short of full disclosure.

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?

Front-loaded with the core action and constrained by a strict read-only caveat at the end; no filler. The long parallel enumeration of topics in a single dense sentence is efficient but somewhat hard to scan, keeping it just below top marks.

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

Completeness5/5

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

Single-parameter tool with no output schema, and the description still says what is returned ("the requested guide only") and what side effects do not occur. Nothing an agent needs in order to invoke it correctly is missing.

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

Parameters5/5

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

Schema coverage is 100%, so baseline would be 3, but the description meaningfully expands each enum value far beyond the schema's bare list ("planning-details for page/multi-page work or unresolved design dependencies"). The agent can pick the right topic from the description alone.

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

Purpose5/5

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

Opens with a specific verb+resource ("Read built-in figlens skill guidance for this agent") and then disambiguates the seven guides by purpose (build for design-to-code, audit for comparing UI, images for asset prep, etc.). Sibling tools like inspect/tree/search are design-data tools, and the final sentence explicitly routes ordinary design questions and exports back to them, so an agent can distinguish this tool without opening the schema.

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

Usage Guidelines5/5

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

Every enum value carries an explicit when-to-use condition ("audit for comparing existing UI with a design and correcting confirmed differences", "yolo for explicitly requested autonomous implementation"), which is effectively a routing table. It also states the exclusion case: "Ordinary design questions and exports can use the design tools directly."

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