Skip to main content
Glama
MCP Dokploy Online
by igoruam

project-search

Read-onlyIdempotent

Search Dokploy projects by name, description, or query text, then paginate results with limit and offset controls.

Instructions

GET /project.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": "project-search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
nameNo
limitNo
offsetNo
descriptionNo

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, idempotentHint and openWorldHint, so the safety profile is covered structurally. The description adds nothing beyond that - no note on pagination behavior, default page size, or result ordering - but it also does not contradict the annotations.

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 short, but this is under-specification rather than conciseness - a bare endpoint path that carries zero usable information. Brevity is not a virtue when nothing is communicated.

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?

A five-parameter search tool with no output schema and no annotation-level detail about results needs the description to explain filter semantics and pagination; it does none of that. The definition is essentially unusable for correct invocation without opening the schema and guessing.

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?

All five parameters (q, name, limit, offset, description) have 0% schema description coverage, and the description supplies no meaning for any of them. Crucially, it does not explain how free-text q differs from the exact-match name and description filters, which is the main ambiguity an agent would face.

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?

"GET /project.search" only restates the tool name as an HTTP route; it names no verb like "search projects by name or description" and gives no hint of what is searched or returned. It is tautological rather than descriptive, and offers no differentiation from siblings like project-all or application-search.

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 when-to-use guidance, no mention of alternatives, and no exclusions. An agent cannot tell from this text why it would pick project-search over project-all or project-one.

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