agent-exec

Search the agent-exec directory

search_listings

Read-only

Free, unauthenticated search over agent-exec's directory of paid agent-facing services (same data as GET https://agent-exec.45.67.221.128.sslip.io/listings). Returns a page of listings and an opaque cursor for the next page.

Input Schema

TableJSON Schema

Name	Required	Description
`tag`	No	Filter to listings carrying this tag.
`limit`	No	Max listings to return (server-bounded regardless).
`cursor`	No	Opaque pagination cursor from a previous call's nextCursor.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No
`listings`	No
`nextCursor`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed5 schema fields changedSep 5, 2026

addedOutput schema / properties / listings / items / properties / consecutiveFailures
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / listings / items / properties / deadSince
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
addedOutput schema / properties / listings / items / properties / evictsAt
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
addedOutput schema / properties / listings / items / properties / remedy
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

changedOutput schema / properties / listings / items / required

Previous value: -[
-  "url",
-  "name",
-  "description",
-  "tags",
-  "tier",
-  "lastSeenAlive",
-  "paidUntil",
-  "dead",
-  "lastProbeCode",
-  "operator"
-]New value: +[
+  "url",
+  "name",
+  "description",
+  "tags",
+  "tier",
+  "lastSeenAlive",
+  "paidUntil",
+  "dead",
+  "lastProbeCode",
+  "operator",
+  "consecutiveFailures",
+  "deadSince",
+  "evictsAt",
+  "remedy"
+]

Changed2 schema fields changedSep 5, 2026

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "code": {
+      "const": "LISTINGS_QUERY_INVALID",
+      "type": "string"
+    },
+    "details": {
+      "additionalProperties": {},
+      "type": "object"
+    },
+    "message": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message",
+    "details"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "listings",
-  "nextCursor"
-]

Changed1 schema field changedSep 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "listings": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "dead": {
+            "type": "boolean"
+          },
+          "description": {
+            "type": "string"
+          },
+          "lastProbeCode": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "lastSeenAlive": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "name": {
+            "type": "string"
+          },
+          "operator": {
+            "type": "boolean"
+          },
+          "paidUntil": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "tags": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "tier": {
+            "enum": [
+              "free",
+              "paid"
+            ],
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "url",
+          "name",
+          "description",
+          "tags",
+          "tier",
+          "lastSeenAlive",
+          "paidUntil",
+          "dead",
+          "lastProbeCode",
+          "operator"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "nextCursor": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "listings",
+    "nextCursor"
+  ],
+  "type": "object"
+}

First observedSep 1, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds meaningful behavioral context beyond that: the operation is free and unauthenticated, and it returns a page of listings plus an opaque cursor for subsequent pages. This gives the agent a precise model of access requirements and pagination behavior.

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?

Two sentences with zero waste. The first front-loads the core purpose and constraints (free, unauthenticated, directory of paid services), and the second conveys the return shape and pagination. Every sentence earns its place.

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?

For a simple, zero-required-parameter search tool with a full output schema and read-only annotations, the description is complete. It covers authentication, pagination, and data-source equivalence, while return-value details are left to the output schema as intended. No critical information is missing for correct invocation.

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?

The input schema already documents all three optional parameters with descriptions at 100% coverage, so the description adds no new parameter-level semantics. Per the calibration baseline, 3 is appropriate when the schema carries the full burden and the description merely references the cursor without elaborating further.

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 states a specific verb ('search') applied to a specific resource ('agent-exec's directory of paid agent-facing services') and explicitly equates the data to a named GET endpoint. This leaves no ambiguity about what the tool does and naturally distinguishes it from the sibling service_card, which appears to target a single listing.

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

Usage Guidelines4/5

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

It provides clear context: use this for a free, unauthenticated search over the directory, and it notes the data is identical to a specific HTTP endpoint. It doesn't explicitly contrast this with service_card or state when not to use it, so it stops short of a 5, but the context is strong enough for an agent to make a sensible routing decision.

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

All agent-exec tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

The two tools have clear, non-overlapping roles: search_listings handles discovery and pagination over the catalog, while service_card provides purchase details and payment instructions. There is no realistic scenario where an agent would confuse which tool to use.

Naming Consistency3/5

search_listings follows a verb_noun pattern, but service_card is a bare noun phrase and lacks an action verb like get_ or fetch_. The names are readable and distinguishable, but the conventions are mixed.

Tool Count3/5

Two tools is on the thin side for a directory-oriented server, but each tool serves a distinct step in the discover-then-purchase flow. It is a borderline count rather than well-scoped or excessive.

Completeness4/5

For the apparent consumer-facing purpose, the core loop is covered: search listings to find a service, then get the service card for pricing and payment URL. A few extras like filtering, categories, or a dedicated listing-detail tool would round it out, but there are no major dead ends.

Resources

Need Help?