Skip to main content
Glama
MCP Dokploy Online
by igoruam

application-search

Read-onlyIdempotent

Search Dokploy applications by name, owner, project, environment, repository, or Docker image to locate deployments matching specific criteria.

Instructions

GET /application.search

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": "application-search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
nameNo
limitNo
ownerNo
offsetNo
appNameNo
projectIdNo
repositoryNo
descriptionNo
dockerImageNo
environmentIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered without the description. The description adds nothing beyond that — no note on result volume, whether all filters are ANDed, or how q differs from name/appName/description — and only implicitly corroborates that this is a read via "GET".

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is certainly short and front-loaded, but the brevity is under-specification rather than economy — the single endpoint token earns nothing that the tool name does not already convey.

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

Completeness1/5

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

For a tool with eleven undocumented optional filters, no output schema, and no required parameters, the definition leaves an agent unable to construct a meaningful query or predict the response shape.

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

Parameters1/5

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

Eleven parameters with 0% schema description coverage and no required fields; the description says nothing about any of them. With zero schema documentation, the description was the only place to explain q vs name vs appName, the default limit of 20, or offset paging, and it supplies none of that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is the raw endpoint string "GET /application.search", which merely restates the tool name (application-search) in HTTP form. It implies searching applications, but gives no verb-level statement of what is searched or returned, so it barely distinguishes this from the many sibling *-search tools beyond the name already supplied.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus project-search, environment-search, or the other search siblings, nor any note about prerequisites, exclusivity of the filter parameters, or pagination behavior.

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