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.

Changed6 schema fields changedSep 6, 2026

addedOutput schema / properties / listings / items / properties / claim
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / listings / items / properties / claimable
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / listings / items / properties / id
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / listings / items / properties / ownerVerifiedAlternate

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "signedByOwner": {
+      "type": "boolean"
+    },
+    "url": {
+      "type": "string"
+    },
+    "verifiedVia": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "url",
+    "verifiedVia",
+    "signedByOwner"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / listings / items / properties / provenance

Added value: +{
+  "enum": [
+    "owner",
+    "operator",
+    "curated"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / listings / items / required

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

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

A3.6/5.0

Behavior4/5

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

With readOnlyHint=true and destructiveHint=false, the description adds meaningful context: the search is free, unauthenticated, backed by a public GET endpoint, and returns paginated results with an opaque cursor. This goes beyond annotations without contradicting them.

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 no wasted text. The most important facts (free, unauthenticated, data source, pagination) are front-loaded and every clause earns its place.

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?

The tool is simple (three optional params, no required fields, output schema present). The description covers the core behavioral contract, including pagination and the underlying data source. Mentioning the sibling tool would improve completion, but nothing essential is missing.

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 100%, with all three parameters already described in the input schema. The description adds no new parameter meaning beyond what the schema provides; the baseline of 3 applies.

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?

The description uses a specific verb ('search') and a clear resource ('agent-exec's directory of paid agent-facing services'), and adds the endpoint equivalent. It does not explicitly contrast with the sibling service_card, but the function is still clearly distinguishable.

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

Usage Guidelines2/5

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

The description gives no guidance about when to use this tool instead of service_card, and does not mention any exclusions. It notes the search is free and unauthenticated, which is useful context but not guidance on choosing between tools.

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

A3.9/5.0

Disambiguation5/5

The two tools serve clearly distinct purposes: one searches the directory, the other returns details about a specific service. There is no overlap or ambiguity between them.

Naming Consistency3/5

search_listings follows a verb_noun pattern, while service_card is a noun_noun phrase. With only two tools, this 50% deviation makes the naming convention noticeably inconsistent, though both use readable snake_case.

Tool Count3/5

Two tools feels thin for a typical server, but for a read-only directory discovery role, search and detail retrieval may be sufficient. The count is borderline but not unreasonable.

Completeness4/5

The surface covers the core flow of discovering services and fetching purchase details. Since payment happens over plain HTTP outside MCP, no additional operations are strictly needed, though a filter or category listing could be a minor enhancement.

Resources

Need Help?