Skip to main content
Glama
john-broadway

Proximo

by john-broadway
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

proximo_find_tools

Read-only

Search Proximo's tool catalog by keyword to locate tools for Proxmox VE management. Get schemas and run commands from the results.

Instructions

Search Proximo's full tool catalog by keyword.

ESTATE QUESTIONS FIRST: if the question is what exists, how many, what changed, or when something last happened, call proximo_recall instead — it answers from local memory in one call, with no search and no schema lookup, and it stamps how old the answer is. Come here for everything else.

The facade is resident; 924 more tools on this server are searchable but not. Search for what you want ("guest power", "ceph pool", "firewall"), then call proximo_tool_schema on a result to get its arguments, then proximo_read (read-only tools) or proximo_call to run it. All terms must match.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.32.0
    • addedOutput schema / properties / result / anyOf
      Added value: +[
+  {
+    "items": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "additionalProperties": true,
+    "type": "object"
+  }
+]
    • removedOutput schema / properties / result / items
      Removed value: -{
-  "additionalProperties": true,
-  "type": "object"
-}
    • removedOutput schema / properties / result / type
      Removed value: -"array"
  2. Addedv0.31.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries the rest: it discloses that the facade is resident, that 924 tools are searchable but not resident, and that all terms must match (AND semantics). It stops short of describing result ordering or how the non-resident tools are surfaced.

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?

Front-loads the one-line purpose, then the disambiguation rule and the call sequence. Every sentence carries load, though the 'ESTATE QUESTIONS FIRST' block and workflow paragraph make it longer than a bare search tool strictly needs.

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?

An output schema exists, so return values need no explanation. The description covers scope, routing, matching semantics, and the invocation chain; the only real gap is the undocumented limit parameter.

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% and neither parameter is documented in the schema, so the description must compensate. 'All terms must match' usefully explains the query parameter's matching semantics, but the limit parameter (default 25) is never mentioned, leaving half the surface undocumented.

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?

States a specific verb (search) and resource (Proximo's full tool catalog) with the keyword mechanism. It explicitly contrasts itself against proximo_recall, so an agent can distinguish the two without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit rule for when to call proximo_recall instead ('what exists, how many, what changed, or when something last happened') and frames everything else as this tool's domain. It also lays out the follow-on workflow (proximo_tool_schema, then proximo_read/proximo_call), which is exactly the routing an agent needs.

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