Echo RunPod

Echo SDK Invoke

invoke_sdk_cap

Destructive

Invoke an Echo SDK capability by exact ID with parameters, passing confirmation for risky calls and an idempotency key to retry safely.

Instructions

Invoke an Echo SDK capability by exact capability ID with params. Risky caps require confirm='SDK_INVOKE_APPROVED' unless ECHO_MCP_ALLOW_RISKY_SDK=1. Supports idempotency_key + gate retry/backoff.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "capability": "<capability>"
    },
    "name": "invoke_sdk_cap"
  }
}

Input Schema

Name	Required	Description
`params`	No
`reason`	No
`confirm`	No
`payload`	No
`capability`	Yes
`idempotency_key`	No	Optional key for safe retries of mutating invokes.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1Oct 3, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare this as non-read-only and destructive, but the description adds valuable behavioral context: risky invocations require an approval token or env override, and idempotency_key plus retry/backoff are supported. It still leaves undefined what risky means and what side effects occur.

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?

The description is three short, front-loaded sentences with no filler. Purpose, gating requirements, and retry support are each communicated efficiently.

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?

For a destructive six-parameter tool with nested objects, the description covers the key approval and retry mechanics, and an output schema exists. However, with very low schema description coverage, it should do more to explain reason, payload, and params semantics.

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

Parameters2/5

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

Schema description coverage is only 17%, so the description must compensate. It gives some meaning for capability, confirm, and idempotency_key, but it does not explain reason, payload, or the shape and semantics of params, leaving most parameters without meaningful 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?

The description states a specific verb and resource: invoking an Echo SDK capability by exact capability ID with params. It is clear what the tool does, but it does not explicitly differentiate itself from the sibling tools search, write, and read.

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?

It gives an important usage condition for risky capabilities: confirm='SDK_INVOKE_APPROVED' unless ECHO_MCP_ALLOW_RISKY_SDK=1. However, it does not say when to use this tool versus alternatives such as search, write, or read, nor does it define what counts as a risky capability.

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

Deploy Server