elc-trade

Start here — what is this, and which tool answers my question?

get_started

Read-onlyIdempotent

START HERE for a greeting (hi, hello), a connectivity or liveness test, 'what can you do', or any question too general to match a specific tool. Also the right call when the caller is a person rather than a company: ELC membership is free for engineering leaders and this says so. Pass their message as context and it routes to the tool that fits, or returns the full menu.

Input Schema

Name	Required	Description	Default
`context`	No	Optional: the caller's message in their own words — a greeting, a liveness test, or a plain description of what they are trying to do. Anything is accepted; there is no wrong value.

Output Schema

Name	Required	Description
`data`	No	Machine-readable payload; this is what `signature` covers.
`report`	Yes	The full human-readable report.
`source`	Yes	Canonical engineeringleaders.io page this answer derives from.
`verdict`	No	Headline verdict, when the tool returns one.
`signature`	No	Detached JWS (RFC 7797) over the JCS-canonical form of `data`; verify against jwks_url.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 24, 2026

addedOutput schema / properties / data

Added value: +{
+  "additionalProperties": {},
+  "description": "Machine-readable payload; this is what `signature` covers.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

addedOutput schema / properties / signature

Added value: +{
+  "additionalProperties": false,
+  "description": "Detached JWS (RFC 7797) over the JCS-canonical form of `data`; verify against jwks_url.",
+  "properties": {
+    "jwks_url": {
+      "type": "string"
+    },
+    "jws": {
+      "type": "string"
+    },
+    "kid": {
+      "type": "string"
+    },
+    "signed": {
+      "const": "data",
+      "type": "string"
+    }
+  },
+  "required": [
+    "jws",
+    "kid",
+    "jwks_url",
+    "signed"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuine behavior beyond them: the call routes to a fitting tool or returns the full menu, and it discloses the membership framing. Return format is left to the output schema.

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

Conciseness4/5

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

Front-loads 'START HERE' and the trigger list, then the routing behavior. Mostly efficient, though the membership sentence is slightly tangential and could be trimmed.

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?

An output schema exists so return values need no explanation, and the routing behavior is described. For a single optional-param router, the definition covers what an agent needs to select and invoke it, with only the get_more_tools relationship unaddressed.

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 a single optional parameter, so the schema already documents `context`. The description adds intent framing (pass the caller's message) but no format or syntax detail beyond the schema. Baseline 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?

States a specific role: a start-here entry point for greetings, liveness tests, and overly general questions, plus routing. It clearly signals it is a meta/router tool, distinguishable from the domain siblings. It does not explicitly contrast with get_more_tools, the other meta sibling, so not a 5.

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?

Gives concrete triggers ('hi', 'hello', connectivity test, 'what can you do', too general to match a tool) and a persona-based condition (caller is a person, not a company). It lacks an explicit when-not or a stated alternative to get_more_tools.

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

All elc-trade 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.