Chain.Love MCP

Unified Execute

execute

Unified execution entrypoint for registry actions, saved connection management, downstream MCP connection validation, and downstream MCP runtime actions

Input Schema

TableJSON Schema

Name	Required	Description
`analytics`	No	Optional analytics context. It is ignored by tool execution and recorded only for usage analytics.
`arguments`	No	Operation-specific arguments. Preferred runtime flow uses create_connection or bind_credentials_bag, then connect_mcp, then connection_id for list_mcp_tools and call_mcp_tool
`operation`	No	Unified operation name: get_details \| open_actions \| connect_mcp \| list_connections \| create_connection \| get_connection \| update_connection_label \| delete_connection \| list_mcps \| bind_mcp_tokens \| list_mcp_tools \| call_mcp_tool
`service_id`	No	Registry service identifier. Required for service-scoped operations such as get_details, open_actions, and connect_mcp

Schema Changelog

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

Changed1 schema field changedAug 13, 2026

addedInput schema / properties / analytics

Added value: +{
+  "description": "Optional analytics context. It is ignored by tool execution and recorded only for usage analytics.",
+  "properties": {
+    "conversation_id": {
+      "description": "Optional conversation identifier.",
+      "type": "string"
+    },
+    "interaction_id": {
+      "description": "Optional interaction/message identifier.",
+      "type": "string"
+    },
+    "source": {
+      "description": "Optional analytics source identifier.",
+      "type": "string"
+    },
+    "user_query": {
+      "description": "Original user query or prompt that led to this tool call, if available.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedApr 15, 2026

TDQS

C2.1/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It only discloses that the analytics parameter is ignored by execution. It does not mention that operations like delete_connection are destructive, that credentials may be required, or anything about side effects. For a tool capable of creating/deleting connections and calling MCP tools, this is a major transparency gap.

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 description is a single long sentence packed with undefined jargon ('registry actions', 'downstream MCP connection validation'). It is not front-loaded with a concrete verb or resource, and it reads as abstract obfuscation rather than concise communication.

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

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This tool has high complexity (4 parameters, nested objects, 12 operations, no output schema, no annotations), yet the description offers only a vague high-level categorization. It omits the list of operations, required/optional parameters, expected return values, side effects, and safety implications. The schema fills some gaps, but the description is completely inadequate for an agent to safely invoke this tool.

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 description coverage is 100%, so the baseline is 3. The tool description adds no parameter-level detail beyond what the schema already provides. The schema's own arguments description contains a useful preferred-flow note, but that is not part of the tool description, so no incremental value is added by the description itself.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Unified execution entrypoint for registry actions, saved connection management, downstream MCP connection validation, and downstream MCP runtime actions' is vague and generic. It lists categories of activity without naming any specific operation or indicating what the tool actually does. The 12 operation names in the schema are not referenced, and the description does not distinguish this tool from siblings like search or discover_categories.

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?

There is no guidance on when to use execute versus the sibling tools. The only usage hint appears in the schema's arguments parameter ('Preferred runtime flow uses create_connection...'), which is part of the schema, not the tool description. The description itself offers no when-to-use or when-not-to-use guidance.

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

All Chain.Love MCP 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

C2.9/5.0

Disambiguation2/5

The 'execute' tool is a catch-all for registry actions, connection management, and runtime actions, creating ambiguity about when to use it versus the more specific discover_* and search tools. The other tools are distinct, but the overlap with execute's broad scope causes confusion.

Naming Consistency2/5

Tool names mix bare verbs ('execute', 'search') with verb-noun patterns ('discover_categories', 'discover_networks'), plus one compound 'bind_credentials_bag'. This inconsistent style violates the predictable convention expected in a well-coherent tool set.

Tool Count4/5

Five tools is within the ideal range for a focused MCP server. The count feels reasonable, though the broad scope of 'execute' suggests it may be absorbing many operations that could be split into more distinct tools.

Completeness3/5

The server covers discovery, search, and credential binding, but the generic 'execute' tool is the only gateway to mutations and connection management. This makes the surface technically complete but poorly structured, as significant functionality is hidden inside a single opaque entrypoint.

Resources

Need Help?