Skip to main content
Glama

lookup_soap_operations

Find Workday SOAP service operations, application names, and WSDL URLs before writing cc:workday-out-soap steps. Pass service_name="list" to browse all services by category.

Instructions

Look up Workday SOAP web service operations for use in cc:workday-out-soap steps. Returns the valid application name, common operations, WSDL URL, and notes for a given service. Use this before writing a cc:workday-out-soap step to confirm the correct application name and what operations are available. Pass service_name="list" to see all 37 services grouped by category.

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": {
      "service_name": "<service_name>"
    },
    "name": "lookup_soap_operations"
  }
}

Input Schema

NameRequiredDescriptionDefault
service_nameYesWorkday service name (e.g. "Human_Resources", "Staffing", "Payroll_Interface") or "list" to see all services

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does state that it is a read-only reference lookup and what fields come back. It does not discuss failure behavior for an invalid service name, caching, or whether results are static metadata versus live service queries — the only meaningful gaps for a lookup tool.

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?

Three sentences, front-loaded with purpose followed by guidance and the list shortcut. Every sentence contributes distinct information with no filler or restatement of the name.

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 single-parameter lookup with no output schema and no annotations, the description covers purpose, when to call it, the enumeration shortcut, and the returned fields. Only edge-case behavior (invalid service name, empty results) is unaddressed, which is minor here.

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

Parameters4/5

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

Schema coverage is 100%, so the single parameter is already documented, and the description repeats the "list" sentinel value. It does add meaning beyond the schema by noting there are 37 services and that list mode groups them by category, which helps an agent interpret the response.

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?

The description pairs a specific verb ("Look up") with a specific resource (Workday SOAP web service operations) and names the consuming context (cc:workday-out-soap steps). It also enumerates the return payload — application name, common operations, WSDL URL, notes — so an agent knows exactly what it gets back, and it is clearly distinct from the assembly/XSL/file sibling tools.

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

Usage Guidelines4/5

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

It gives an explicit workflow trigger: call this before writing a cc:workday-out-soap step to confirm the application name and available operations. The discovery path (service_name="list" to enumerate all 37 services) is also spelled out. It lacks an explicit when-not or named alternative tool, which keeps it below a 5.

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