agentswitchboard

Get Agent Details

get_agent

Read-onlyIdempotent

Full detail for one agent by slug: skills, auth, streaming/push support, tags, provider links, and useItNow: how to start using it (MCP client config, install command, API base URL, setup links). Verified: we checked it works — its URLs load and its declared access (API, MCP, CLI or extension) responds. Re-checked monthly; the label drops if it stops working. Official: a first-party listing, published by the company behind the product under its own domain or GitHub org (e.g. Notion's own Notion MCP, not a community build), where that company is a major vendor (publicly traded, a frontier AI lab, or valued around $1B+). It records who publishes the product, not a paid placement, and is separate from Verified. Featured: set only by the maintainer. With no search text, results list featured listings first, then A→Z; with search text, results are ranked by relevance and equal scores keep that featured-first order.

Input Schema

Name	Required	Description	Default
`slug`	Yes	Agent slug, e.g. "playwright-mcp"

Output Schema

Name	Required	Description
`url`	Yes
`name`	Yes
`slug`	Yes
`tags`	Yes
`skills`	Yes
`addedAt`	No
`iconUrl`	Yes	Absolute URL of the listing's 128px PNG icon, served by Agent Switchboard; null when it has none
`install`	Yes	The command that installs its CLI
`agentUrl`	Yes
`authType`	Yes
`featured`	Yes	Featured: set only by the maintainer. With no search text, results list featured listings first, then A→Z; with search text, results are ranked by relevance and equal scores keep that featured-first order.
`official`	Yes	Official: a first-party listing, published by the company behind the product under its own domain or GitHub org (e.g. Notion's own Notion MCP, not a community build), where that company is a major vendor (publicly traded, a frontier AI lab, or valued around $1B+). It records who publishes the product, not a paid placement, and is separate from Verified.
`provider`	Yes
`useItNow`	Yes	How to start using it, per access method: client config and install links for MCP, the install command for a CLI, base URL and auth for an API. Commands and addresses come from the vendor's own docs; when there are none, docsUrl is where its instructions are.
`verified`	Yes	Verified: we checked it works — its URLs load and its declared access (API, MCP, CLI or extension) responds. Re-checked monthly; the label drops if it stops working.
`apiBaseUrl`	Yes	Base URL of the vendor's public API
`categories`	Yes
`mcpCommand`	Yes	The command that runs its MCP server locally
`description`	Yes
`mcpEndpoint`	Yes	The vendor's hosted MCP server address
`providerUrl`	Yes
`accessMethods`	Yes
`quickstartUrl`	Yes	The vendor's setup or getting-started page
`officialVendor`	Yes
`supportsStreaming`	Yes
`supportsPushNotifications`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 25, 2026

addedOutput schema / properties / featured

Added value: +{
+  "description": "Featured: set only by the maintainer. With no search text, results list featured listings first, then A→Z; with search text, results are ranked by relevance and equal scores keep that featured-first order.",
+  "type": "boolean"
+}

changedOutput schema / properties / official / description

Previous value: -"First-party listing from a major vendor"New value: +"Official: a first-party listing, published by the company behind the product under its own domain or GitHub org (e.g. Notion's own Notion MCP, not a community build), where that company is a major vendor (publicly traded, a frontier AI lab, or valued around $1B+). It records who publishes the product, not a paid placement, and is separate from Verified."

addedOutput schema / properties / verified / description

Added value: +"Verified: we checked it works — its URLs load and its declared access (API, MCP, CLI or extension) responds. Re-checked monthly; the label drops if it stops working."

changedOutput schema / required

Previous value: -[
-  "name",
-  "slug",
-  "description",
-  "provider",
-  "categories",
-  "accessMethods",
-  "authType",
-  "verified",
-  "official",
-  "officialVendor",
-  "url",
-  "agentUrl",
-  "providerUrl",
-  "skills",
-  "tags",
-  "supportsStreaming",
-  "supportsPushNotifications"
-]New value: +[
+  "name",
+  "slug",
+  "description",
+  "provider",
+  "categories",
+  "accessMethods",
+  "authType",
+  "verified",
+  "official",
+  "officialVendor",
+  "featured",
+  "url",
+  "agentUrl",
+  "providerUrl",
+  "skills",
+  "tags",
+  "supportsStreaming",
+  "supportsPushNotifications"
+]

Changed3 schema fields changedOct 11, 2026

addedOutput schema / properties / official

Added value: +{
+  "description": "First-party listing from a major vendor",
+  "type": "boolean"
+}

addedOutput schema / properties / officialVendor

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "name",
-  "slug",
-  "description",
-  "provider",
-  "categories",
-  "accessMethods",
-  "authType",
-  "verified",
-  "url",
-  "agentUrl",
-  "providerUrl",
-  "skills",
-  "tags",
-  "supportsStreaming",
-  "supportsPushNotifications"
-]New value: +[
+  "name",
+  "slug",
+  "description",
+  "provider",
+  "categories",
+  "accessMethods",
+  "authType",
+  "verified",
+  "official",
+  "officialVendor",
+  "url",
+  "agentUrl",
+  "providerUrl",
+  "skills",
+  "tags",
+  "supportsStreaming",
+  "supportsPushNotifications"
+]

Changed1 schema field changedSep 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "accessMethods": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "addedAt": {
+      "type": "string"
+    },
+    "agentUrl": {
+      "type": "string"
+    },
+    "authType": {
+      "type": "string"
+    },
+    "categories": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "description": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "provider": {
+      "type": "string"
+    },
+    "providerUrl": {
+      "type": "string"
+    },
+    "skills": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "description": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "description"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "slug": {
+      "type": "string"
+    },
+    "supportsPushNotifications": {
+      "type": "boolean"
+    },
+    "supportsStreaming": {
+      "type": "boolean"
+    },
+    "tags": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "url": {
+      "type": "string"
+    },
+    "verified": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "name",
+    "slug",
+    "description",
+    "provider",
+    "categories",
+    "accessMethods",
+    "authType",
+    "verified",
+    "url",
+    "agentUrl",
+    "providerUrl",
+    "skills",
+    "tags",
+    "supportsStreaming",
+    "supportsPushNotifications"
+  ],
+  "type": "object"
+}

First observedJul 24, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already cover read-only, idempotent and non-destructive behavior, so the description's useful addition is data semantics: monthly re-checks and what the Verified/Official/Featured labels actually attest. However, it never clarifies failure behavior for an unknown slug or how official vs community listings differ in trust for the caller, and much of the label text reads like catalog-policy prose rather than tool behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is well front-loaded, but the bulk of the text defines Verified, Official, and Featured labels, then closes with result-ordering rules ('featured listings first, then A→Z; with search text, results are ranked by relevance') that cannot apply to a single-record fetch — pure bloat that dilutes the actionable content.

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

Completeness3/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 needn't be spelled out, yet the description spends most of its length on field-label policy rather than the call itself. It is adequate to invoke the tool but omits not-found handling and any hint about payload size, while over-serving irrelevant list-ordering context.

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?

There is one parameter at 100% schema description coverage with an inline example ('playwright-mcp'), so the schema already does the work. The description only restates that lookup is by slug and adds no format, case-sensitivity, or not-found guidance.

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?

Opens with a specific verb+resource+scope: 'Full detail for one agent by slug', then enumerates the returned fields (skills, auth, streaming/push, tags, provider links, useItNow). That distinguishes it from search_agents/compare_agents as a single-record fetch, though no sibling is named directly.

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?

Usage is only implied by 'one agent by slug' — the agent can infer this is the follow-up to a search result, but there is no explicit when-to-use or when-not-to-use versus search_agents or compare_agents.

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

All agentswitchboard tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.