Skip to main content
Glama

deployment_listResources

Lists all BPMN, DMN, and form resources in a deployment by deployment ID, helping you verify exactly what was deployed.

Instructions

List all resources (BPMN files, DMN files, forms) included in a deployment by deployment ID.

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": {
      "id": "<id>"
    },
    "name": "deployment_listResources"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.0
    • addedInput schema / properties / id
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "id"
      +]
  2. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/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. 'List' implies a read, and naming the resource types is genuinely informative, but the description says nothing about pagination, ordering, error behavior for an unknown ID, or the shape of the returned resource entries. For a tool with zero annotation coverage that is a meaningful gap, though the low-risk read nature keeps it from being a 1.

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?

One sentence, front-loaded with the operation and scoping key, with the resource enumeration placed where it is most useful. No filler, no restating of the tool name.

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?

For a single-parameter read tool, the core need — what it returns and which ID to pass — is covered. However, with no output schema and no annotations, the description should have said more about the returned structure (identifiers, names, resource types) and whether the list is complete or paginated.

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?

The schema has one parameter literally named 'id' with 0% description coverage, which is genuinely ambiguous. The description resolves it directly by stating the parameter is the deployment ID. That is exactly the clarification the schema lacks, and it is the main thing an agent needs; format or validation details are omitted.

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 gives a specific verb and resource ('List all resources') plus the scoping key ('included in a deployment by deployment ID') and enumerates what counts as a resource: BPMN files, DMN files, forms. It is clearly distinguishable from siblings like deployment_list and deployment_count. It stops short of distinguishing itself from deployment_getById, which could plausibly also return deployment contents.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no prerequisites (e.g., the deployment must exist), and no reference to any alternative tool. The agent must infer that this is the right call whenever it happens to need a deployment's contents.

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

Deploy Server

Other Tools