Skip to main content
Glama

protogrid

by dev.protogrid
OverviewDiscussionsAdmin

List a server's tools

list_tools
Read-onlyIdempotent

Every current tool of a server with full input/output schemas, paginated by tool name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesOfficial reverse-DNS name
limitNo
cursorNonext_cursor from the previous page

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
toolsYes
serverYes
next_cursorYesPass as cursor for the next page; null on the last page
next_actionsYesFollow-up calls: action is the tool, arguments are ready to pass ({placeholders} are yours to fill)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "count": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "next_actions": {
+      "description": "Follow-up calls: action is the tool, arguments are ready to pass ({placeholders} are yours to fill)",
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "action": {
+            "type": "string"
+          },
+          "arguments": {
+            "additionalProperties": {},
+            "propertyNames": {
+              "type": "string"
+            },
+            "type": "object"
+          }
+        },
+        "required": [
+          "action"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "next_cursor": {
+      "description": "Pass as cursor for the next page; null on the last page",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "server": {
+      "type": "string"
+    },
+    "tools": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "annotations": {
+            "description": "Tool hints such as readOnlyHint, as the server declares them"
+          },
+          "description": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "input_schema": {
+            "description": "JSON Schema of the arguments, as the server declares it"
+          },
+          "name": {
+            "type": "string"
+          },
+          "observed_at": {
+            "type": "string"
+          },
+          "output_schema": {},
+          "source": {
+            "enum": [
+              "probe",
+              "publisher"
+            ],
+            "type": "string"
+          },
+          "title": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "name",
+          "title",
+          "description",
+          "input_schema",
+          "output_schema",
+          "annotations",
+          "source",
+          "observed_at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "server",
+    "count",
+    "tools",
+    "next_cursor",
+    "next_actions"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorldHint=false, so the safety profile is covered by structured data. The description adds that results are paginated and that schemas are returned in full, which is useful context beyond annotations. It does not disclose ordering guarantees besides 'by tool name' or limits.

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?

A single tightly packed sentence that front-loads the core action and scope with no wasted words.

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?

A read-only, paginated list tool. The description covers the return content and pagination, and an output schema exists so return values needn't be explained. Missing only the 'limit' parameter meaning, which keeps it short of a 5.

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 67%, with 'name' and 'cursor' documented in the schema; 'limit' has no description. The description repeats the pagination concept but adds no parameter-level detail beyond what the schema provides, so baseline 3 is appropriate.

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 ('List ... tools of a server') and adds scope detail ('full input/output schemas, paginated by tool name'). It does not differentiate from siblings like search, though the resource is distinct enough to be inferred.

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?

The pagination mention implies iterative use with the cursor, and the framing suggests this is the enumeration endpoint. But there is no explicit when-to-use vs alternatives (e.g., search for filtered lookup), so usage is only implied.

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

All protogrid toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources