Agent Einstein — Crypto & Market Intelligence

List Einstein Capabilities

list_einstein_capabilities

Read-onlyIdempotent

Everything Einstein can do through this connector, split into free tools and paid tools with their prices, plus how billing works. Call this when you are not sure which tool fits, or before telling a user something isn't available.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`free`	No	Tools any caller can use with no account and no charge.
`paid`	No	Tools that need a signed-in Einstein account with credit.
`reason`	No	Why the payload is absent, when `available` is false.
`billing`	No	How paying works: the billing model, how to top up and how to sign in.
`available`	No	False when this call has no data. NOT an error.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "available": {
+      "description": "False when this call has no data. NOT an error.",
+      "type": "boolean"
+    },
+    "billing": {
+      "additionalProperties": true,
+      "description": "How paying works: the billing model, how to top up and how to sign in.",
+      "type": "object"
+    },
+    "free": {
+      "description": "Tools any caller can use with no account and no charge.",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "description": {
+            "description": "What it returns.",
+            "type": "string"
+          },
+          "name": {
+            "description": "Tool name to call.",
+            "type": "string"
+          },
+          "title": {
+            "description": "Human-readable title.",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "paid": {
+      "description": "Tools that need a signed-in Einstein account with credit.",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "description": {
+            "description": "What it returns.",
+            "type": "string"
+          },
+          "name": {
+            "description": "Tool name to call.",
+            "type": "string"
+          },
+          "priceUsd": {
+            "description": "USD price per call, or a range when the tool routes to several skills.",
+            "type": "string"
+          },
+          "title": {
+            "description": "Human-readable title.",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "reason": {
+      "description": "Why the payload is absent, when `available` is false.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedAug 17, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive nature of the tool. The description adds valuable behavioral context by disclosing that it returns a categorized catalog with pricing and billing details, which is beyond what the annotations provide.

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, front-loaded with the tool's purpose and followed by clear usage guidance. Every sentence earns its place with no redundancy or filler.

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 zero-parameter, read-only discovery tool with an output schema and strong annotations, the description is fully adequate. It explains what the output includes and when to invoke it, leaving no critical gap for an agent to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

This tool has zero parameters, so the baseline of 4 applies. There is nothing for the description to clarify in terms of parameter meaning, and it rightly does not invent any.

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 uses a specific verb ('list') and a clear resource ('Einstein capabilities through this connector'), and further specifies the output is split into free and paid tools with prices and billing info. This clearly differentiates it from the many analysis/get sibling tools.

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 explicitly states when to call: when unsure which tool fits or before telling the user something isn't available. It does not equally explicitly state when not to use it or name alternative tools, but the guidance is clear enough for an agent to route to it appropriately.

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

All Agent Einstein — Crypto & Market Intelligence 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.