Skip to main content
Glama

deployment_list

List engine deployments and filter them by name, source, time range, or tenant to retrieve deployment IDs, names, and timestamps for auditing and tracking.

Instructions

List deployments in the engine. Filter by name, source, deployment time range, or tenant. Returns deployment ID, name, and time for each deployment.

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": "deployment_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
nameNo
afterNo
beforeNo
sortByNo
sourceNo
nameLikeNo
sortOrderNo
maxResultsNo
tenantIdInNo
firstResultNo
withoutSourceNo
withoutTenantIdNo
includeDeploymentsWithoutTenantIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changedv1.3.0
    • addedInput schema / properties / after
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / before
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / firstResult
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / id
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / includeDeploymentsWithoutTenantId
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / maxResults
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / name
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / nameLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / sortBy
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / sortOrder
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / source
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / tenantIdIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / withoutSource
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / withoutTenantId
      Added value: +{
      +  "type": "boolean"
      +}
  2. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the returned fields (ID, name, time), but says nothing about pagination defaults, result limits, sort behavior, permission requirements, or how the 'without*' filters alter results, which matters for a 14-parameter listing tool.

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?

Two sentences, front-loaded with the operation and followed by filters and return shape; there is no wasted wording. It is efficient, though it could have spent a few more words on the undocumented parameters.

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

Completeness2/5

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

For a tool with 14 optional parameters, zero annotation coverage, and no output schema, the description is thin: it covers the return fields but omits pagination, sorting, and the semantics of the negative filters. An agent could call it, but not confidently tune the query.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for all 14 parameters. It only maps meaning onto roughly name, source, time range, and tenant, leaving id, nameLike, sortBy, sortOrder, maxResults, firstResult, withoutSource, withoutTenantId, and includeDeploymentsWithoutTenantId entirely undocumented.

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 states a specific verb and resource ('List deployments in the engine') and names the filterable dimensions, which lets an agent distinguish it from deployment_getById and deployment_count. It stops short of explicitly contrasting with those siblings, so it is clear but not fully differentiated.

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

Usage Guidelines3/5

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

The sentence 'Filter by name, source, deployment time range, or tenant' implies the query use case, but there is no explicit statement of when to prefer this over deployment_count or deployment_getById, and no prerequisites or exclusions are given. Usage is inferable rather than guided.

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