Skip to main content
Glama
Sign In
nimbus

nimbus

by nimbus-agent
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

getRecentDeployments

Retrieve recent deployments sorted newest first, with optional service filtering to focus on specific services.

Instructions

List recent deployments from the local index (most recent first). Optionally filter by service.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
serviceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.14.2

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It adds useful context about the data source (local index), ordering (most recent first), and filtering (by service). However, it does not disclose read-only status, rate limits, or return format details.

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?

The description is a single, front-loaded sentence with no filler. Every phrase contributes meaning, making it highly concise and well-structured.

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?

Given the simple two-parameter tool with no output schema, the description covers essential behavior: what it lists, the data source, ordering, and optional filter. It does not explain return structure, but that is not critical for a simple list operation.

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?

Schema coverage is 0%, so the description must compensate. It explains the 'service' parameter's purpose (filtering) but does not elaborate on 'limit' beyond what the schema type implies. Some meaning is added, but not complete coverage.

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 clearly states the tool lists recent deployments from the local index, with most recent first and optional service filtering. This specific verb+resource+scope distinguishes it from siblings like getRecentPullRequests and getDoraMetrics.

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 description implies usage for retrieving recent deployments with optional service filtering, but does not explicitly state when to use this tool instead of others like searchIndex. There are no exclusions or alternatives mentioned.

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