Cortex

Searchdeploys

searchDeploys

Get deployments with server-side filtering (environment, type, entity, time range). Pass entityTagOrIds=['my-tag'] to get deployments for a single entity, or omit it to search tenant-wide.

Environments are matched exactly — call listDeployEnvironments first to discover values (e.g. 'prod' vs 'prod2ndmd').

Input Schema

TableJSON Schema

Name	Required	Description
`page`	Yes	Page number to return, 0-indexed. Default 0.
`types`	No	Filter by deploy types: DEPLOY, ROLLBACK, SCALE, RESTART
`context`	Yes	Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your overall objective and fits into your broader plan across all tool calls (e.g., why this tool vs. others, and what step it unblocks). Never share any personal details or sensitive information.
`pageSize`	Yes	Number of results to return per page, between 1 and 1000. Default 250.
`session_id`	Yes	Session continuity handle, one of two values: the ses_ ID issued for the task underway, or start. This server cannot link your calls between requests on its own, so session continuity travels in this parameter instead. If you were handed a session_id for this task — for example by the agent that spawned you — send that exact value from your first call. Otherwise send start on your first call; the server will issue an opaque correlation ID in the mcp_session field of the result, or in a text block at the start of the result beginning [session_id issued. Then send that exact ses_ value on every later call and hand it to any subagents working the same task. start always begins a new, unrelated task — never send it mid-task. If you send a value this server does not recognize, the result reports it: mcp_session.status of unrecognized, or a text block beginning [session_id unrecognized; re-send the ID issued for this task, or start if none was issued yet. Never invent a ses_ value.
`environments`	No	Filter by environment names (exact match, any of)
`entityTagOrIds`	No	Filter to these entity tags or CIDs (any of)
`timestampAfter`	No	Only deploys at or after this timestamp (UTC, e.g. 2026-06-22T00:00:00)
`timestampBefore`	No	Only deploys at or before this timestamp (UTC, e.g. 2026-06-22T00:00:00)

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 25, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that filtering is server-side and that environment matching is exact, which is valuable. However, it does not describe pagination behavior, output format, or any limits—though the schema covers pagination parameters. This is adequate but not exhaustive.

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 concise paragraphs with no wasted words. The core purpose and the key gotcha (exact environment matching) are front-loaded, and the usage guidance is directly actionable.

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 9 parameters, 4 required, and no output schema, the description covers the essential filtering behavior and the environment discovery step. It does not explain session_id/context parameters, but those are thoroughly documented in the schema. The lack of output format details is minor for a search tool and the description is sufficient for an agent to call it correctly.

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?

Schema coverage is 100%, so the baseline is 3. The description adds value by explaining the semantic meaning of entityTagOrIds (single entity vs. tenant-wide) and by warning about exact environment matching and the need to discover valid values via listDeployEnvironments. This goes beyond the schema's basic field descriptions.

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 retrieves deployments with server-side filtering by environment, type, entity, and time range. It explicitly distinguishes between single-entity (via entityTagOrIds) and tenant-wide searches, which differentiates it from sibling getDeploysForEntity.

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?

It gives specific guidance on when to pass entityTagOrIds versus omitting it, and instructs to call listDeployEnvironments first for exact environment matching. It does not explicitly mention alternatives like getDeploysForEntity, but the tenant-wide vs. single-entity distinction implies the correct routing.

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

All Cortex tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?