Skip to main content
Glama
john-broadway

Proximo

by john-broadway
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

proximo_find_tools

Read-only

Find the right tool by keyword across the full catalog, then retrieve its schema and run it directly. For estate-status questions, use recall instead.

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; 908 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. Dates show when Glama detected each change.

  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.7/5.0
Behavior5/5

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

Beyond readOnlyHint=true, the description reveals meaningful behavior: the resident/non-resident tool split, keyword matching semantics ('All terms must match'), and that results feed into proximo_tool_schema. This goes well beyond the annotation and does not contradict it.

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?

The description is front-loaded with purpose and the critical routing decision via 'ESTATE QUESTIONS FIRST.' Each sentence carries functional weight—alternatives, workflow, and matching constraints—without fluff. The structure with line breaks aids skimming.

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

Completeness5/5

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

Given the output schema exists, this description sufficiently covers what an agent needs to select and call the tool: purpose, exclusions, workflow, parameter behavior, and search semantics. The only minor ambiguity ('searchable but not') is outweighed by the strong guidance and examples.

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 description coverage is 0%, so the description must compensate. It clarifies the query parameter through 'keyword' and 'All terms must match' with examples ("guest power", "ceph pool", "firewall"), but it never explains limit or how the two parameters interact. Partial compensation only.

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 opens with a specific verb and resource: 'Search Proximo's full tool catalog by keyword.' It is immediately distinguishable from siblings like proximo_recall (state/memory queries), proximo_tool_schema (arguments for a specific tool), and proximo_read/proximo_call (execution). The purpose is unmistakable.

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?

The description explicitly routes the agent: 'if the question is what exists, how many, what changed, or when something last happened, call proximo_recall instead' and 'Come here for everything else.' It also provides a concrete downstream workflow: search, then proximo_tool_schema, then proximo_read or proximo_call.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/john-broadway/proximo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server