Proximo

Overview Schema Source Related Servers Discussions Admin

proximo_find

Read-only

Find Proxmox API addresses by plain-language queries, with the verb selecting the method and results showing access and blast-radius tiers.

Instructions

READ-ONLY: find API addresses by plain words ('list datastores'). A verb picks the method. Returns access and blast-radius tier. 5 by default.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "proximo_find"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`plane`	No
`query`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv0.49.1Oct 27, 2026
- removedInput schema / properties / limit / title
```
Removed value: -"Limit"
```
- removedInput schema / properties / plane / anyOf
```
Removed value: -[
-  {
-    "enum": [
-      "pve",
-      "pbs",
-      "pmg",
-      "pdm"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / plane / default
```
Removed value: -null
```
- addedInput schema / properties / plane / enum
```
Added value: +[
+  "pve",
+  "pbs",
+  "pmg",
+  "pdm"
+]
```
- removedInput schema / properties / plane / title
```
Removed value: -"Plane"
```
- addedInput schema / properties / plane / type
```
Added value: +"string"
```
- removedInput schema / properties / query / title
```
Removed value: -"Query"
```
- removedInput schema / title
```
Removed value: -"findArguments"
```
Addedv0.46.2Oct 24, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description restates READ-ONLY, so it adds little on safety. It does add useful behavior: it returns an 'access and blast-radius tier' and that the limit defaults to 5, which is context beyond 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.

Conciseness4/5

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

Four short, front-loaded sentences with no filler and the READ-ONLY constraint placed first. Slightly telegraphic phrasing ('A verb picks the method') costs a little clarity but wastes no space.

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

Completeness3/5

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

An output schema exists, so return-value explanation is not required. Still, for a 3-param tool with 0% schema coverage, the undocumented 'plane' enum and vague dispatch phrasing leave an agent short of what it needs to call confidently.

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?

With 0% schema coverage, the description must carry parameter meaning. It explains 'query' ('plain words', with an example) and the limit default ('5 by default'), but leaves the 'plane' enum (pve/pbs/pmg/pdm) entirely unexplained, which is a significant gap.

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?

States a specific verb and resource ('find API addresses') and gives a concrete example ('list datastores'), so the discovery intent is clear. 'A verb picks the method' signals this is a dispatcher-style lookup distinct from execution siblings, though the framing is terse.

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?

'READ-ONLY' and 'A verb picks the method' imply this is the search/discovery entry point, hinting it precedes proximo_plan/proximo_call. However, no sibling is named and there is no explicit when-to-use/when-not guidance.

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

Deploy Server