Skip to main content
Glama

get_patterns

Retrieves Workday Studio cross-integration patterns, diagram rules, and MVEL/XSLT guidance from the knowledge base to prevent crashes before editing diagrams or diagnosing logs.

Instructions

Serves the curated Studio knowledge base (docs/studio-integration-patterns.md) — hard-won cross-integration patterns that are NOT tied to a single step type.

CALL THIS PROACTIVELY before: • hand-editing assembly-diagram.xml (swimlanes, @mixed EMF XPath indices, adding/removing/renaming diagram nodes, send-error placement) — the "Diagram Rules" section is the single largest body of gotchas and every rule prevents a scala.MatchError crash on diagram open • writing MVEL, XSLT, RAAS, outbound-HTTP, or document-storage logic • diagnosing a server log or a Common Error

get_step_type_reference covers a SINGLE element; get_patterns covers the cross-cutting rules that span elements (diagram index math, swimlane layout, the three-entry add/remove rule, the verification script, MVEL idioms, etc.).

USAGE: • No arguments → an index of every section and subsection (titles only). Start here, then drill in. • topic="Diagram Rules" → the full section (## or ### heading, partial match ok, case-insensitive). • topic="Insertion shift rule" → a single subsection. • search="swimlane" → every subsection whose heading or body mentions the term.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_patterns"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoA section or subsection title to retrieve (e.g. "Diagram Rules", "Swimlane layout template"). Partial, case-insensitive. Omit to get the index.
searchNoKeyword to find across the whole knowledge base — returns each matching subsection. Takes precedence over topic when both are given.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does most of it: it explains that it is a read of a static knowledge base, what each call mode returns (index of titles vs. full section vs. matching subsections), and matching semantics (partial, case-insensitive, search precedence). It stops short of saying anything about response size, truncation, or what happens when a topic matches nothing, which matters for a section that is described as 'the single largest body of gotchas'.

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 what and the when, and the bulleted CALL THIS PROACTIVELY / USAGE split is easy to scan. Slightly verbose: the topic examples ('Diagram Rules', 'Insertion shift rule', 'swimlane') are given twice and the parenthetical example lists in the first bullet run long.

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

Completeness4/5

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

For a two-parameter retrieval tool with no output schema and no annotations, the description is nearly self-sufficient: it explains inputs, modes, and the shape of each return. The remaining gap is the absence of any guidance on very large sections or on zero-match behavior, which an agent would want before drilling in.

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 coverage is 100% and both schema properties already document partial/case-insensitive matching and search taking precedence over topic. The USAGE block largely restates that with examples, adding little meaning the schema does not already carry, so baseline 3 applies.

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?

States a specific resource (the curated Studio knowledge base) and the precise kind of content it holds: cross-integration patterns not tied to a single step type. It explicitly contrasts itself with get_step_type_reference ('covers a SINGLE element' vs 'cross-cutting rules that span elements'), so an agent can route without opening either 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?

Gives an explicit proactive-call list (hand-editing assembly-diagram.xml, writing MVEL/XSLT/RAAS/outbound-HTTP, diagnosing logs) with the concrete failure each prevents (scala.MatchError on diagram open). It also names the alternative sibling and the boundary condition that selects between them.

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