Skip to main content
Glama

deployment_count

Count process deployments matching filters such as name, source, tenant, and date range to verify how many meet your criteria.

Instructions

Count deployments matching filter criteria. Supports same filters as deployment list.

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_count"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
nameNo
afterNo
beforeNo
sourceNo
nameLikeNo
tenantIdInNo
withoutSourceNo
withoutTenantIdNo
includeDeploymentsWithoutTenantIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv1.3.0
    • addedInput schema / properties / after
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / before
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / id
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / includeDeploymentsWithoutTenantId
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / name
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / nameLike
      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?

No annotations are supplied, so the description bears the full burden. It does not disclose that the result is a scalar count, whether the operation is read-only, what permissions are needed, or how filters combine — all of which are non-obvious for a 10-parameter counting 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 tight sentences, front-loaded with the purpose and no padding. The brevity is appropriate in form but leaves the definition underspecified in substance.

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?

With 10 undocumented parameters, no annotations, and no output schema, the description should explain the return value (a numeric count) and clarify the filter semantics. It supplies neither, leaving significant gaps for a moderately complex query tool.

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% across 10 parameters, so the description must compensate and does not. The deferral 'same filters as deployment list' is not actionable unless the agent already knows that tool's schema, and nothing is said about the meaning of id, name, after/before, nameLike, tenantIdIn, or the without*/include* booleans.

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+resource (count deployments) plus the scoping condition (matching filter criteria), which cleanly separates it from deployment_list and deployment_getById. It stops short of naming a sibling explicitly, but the intent is unambiguous.

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 clause 'Supports same filters as deployment list' implies the tool is a counting counterpart to deployment_list, which is useful routing context. However, it never states when to prefer a count over the list, nor any exclusions or prerequisites.

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