Skip to main content
Glama

list_integration_params

Parse assembly.xml to return StartHere launch parameters and integration attributes, so you can map requirements to the parameter list without reading the full Workday Studio assembly.

Instructions

Parse assembly.xml and return the launch parameters and integration attributes defined on the StartHere (cc:workday-in) element. Use this to map requirements to the param/attribute list without reading the full assembly.

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": {
      "project_name": "<project_name>"
    },
    "name": "list_integration_params"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_nameYesThe Studio project name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It conveys that this is a narrow read/parse of one file and one element, but says nothing about failure modes (missing assembly.xml, malformed XML, absent StartHere element), where project_name resolves to on disk, or how the results are shaped.

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?

Two sentences with no filler: the first front-loads what is parsed and returned, the second gives the reason to use it. Every phrase earns its place.

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, read-only parse tool with no output schema, the description names the source file, the target element, and the kind of data returned, which is close to sufficient. The main gap is error/edge-case behavior, which is minor at this complexity level.

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?

Only one parameter exists and the schema documents it at 100% coverage ('The Studio project name'), so the baseline applies. The description never mentions project_name or clarifies that it determines which assembly.xml is parsed, adding no meaning beyond the schema.

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?

States a specific verb (parse) and a specific resource (assembly.xml), and names the exact element it extracts from (StartHere / cc:workday-in) plus what it returns. It implicitly separates itself from full-file readers with 'without reading the full assembly', though it never names a sibling tool.

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?

'Use this to map requirements to the param/attribute list without reading the full assembly' gives a real usage context and an implicit exclusion (don't use a full-read tool when you only need params). It stops short of naming an explicit alternative such as read_integration_file or stating when this tool would be the wrong choice.

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