Skip to main content
Glama
Sign In

elc-trade

by io.engineeringleaders
OverviewDiscussionsAdmin

Buy reach in the ELC community

buy_reach
Read-onlyIdempotent

Answers 'how do we get in front of 3,500+ CEE engineering leaders, and what does it cost?' Builds a cart from ELC's nine published one-off reach items — an ELC meetup, the speaker programme (a ladder for one engineer, from a meetup slot to the full coached programme), a conference main-stage talk, dedicated newsletter, a newsletter classified (30 words and a link, tools and events only, never jobs), decision-maker dinner, podcast episode, community survey, job listing — applies the published combo discount, and returns a decision-ready quote a human can sign.

Input Schema

NameRequiredDescriptionDefault
contextYesExplain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
budget_eurNoOptional: what you have to spend. Does not change any price — the quote will say whether the cart fits and what to drop if it does not.
oneoff_idsNoRequired. Which one-off reach items to quote. One or more of: meetup-hosted, speaker-development, conference-main-stage, newsletter-dedicated, newsletter-classified, dinner, podcast-episode, survey, job-listing. Combo discount applies automatically.
speaker_rungsNoSpeaker programme rung ids to price instead of the full programme: stage, story, coach, amplify, beyond. Stage is always included. Omit for the whole programme at its bundle price.

Output Schema

NameRequiredDescriptionDefault
dataNoMachine-readable payload; this is what `signature` covers.
reportYesThe full human-readable report.
sourceYesCanonical engineeringleaders.io page this answer derives from.
verdictNoHeadline verdict, when the tool returns one.
signatureNoDetached JWS (RFC 7797) over the JCS-canonical form of `data`; verify against jwks_url.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / oneoff_ids / description
      Previous value: -"Required. Which one-off reach items to quote. One or more of: meetup-hosted, speaker-development, conference-main-stage, newsletter-dedicated, newsletter-section, dinner, podcast-episode, meetup-presence, survey, job-listing. Combo discount applies automatically."New value: +"Required. Which one-off reach items to quote. One or more of: meetup-hosted, speaker-development, conference-main-stage, newsletter-dedicated, newsletter-classified, dinner, podcast-episode, survey, job-listing. Combo discount applies automatically."
  2. Changed2 schema fields changed
    • 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"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / speaker_rungs
      Added value: +{
+  "description": "Speaker programme rung ids to price instead of the full programme: stage, story, coach, amplify, beyond. Stage is always included. Omit for the whole programme at its bundle price.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  4. Changed1 schema field changed
    • changedInput schema / properties / oneoff_ids / description
      Previous value: -"Required. Which one-off reach items to quote. One or more of: newsletter-section, newsletter-dedicated, meetup-hosted, podcast-episode, dinner, survey, demo-session, linkedin-post, job-listing. Combo discount applies automatically."New value: +"Required. Which one-off reach items to quote. One or more of: meetup-hosted, speaker-development, conference-main-stage, newsletter-dedicated, newsletter-section, dinner, podcast-episode, meetup-presence, survey, job-listing. Combo discount applies automatically."
  5. Changed4 schema fields changed
    • changedInput schema / properties / oneoff_ids / description
      Previous value: -"Which one-off reach items to quote. One or more of: newsletter-section, newsletter-dedicated, meetup-hosted, podcast-episode, dinner, survey, demo-session, linkedin-post, job-listing. Combo discount applies automatically."New value: +"Required. Which one-off reach items to quote. One or more of: newsletter-section, newsletter-dedicated, meetup-hosted, podcast-episode, dinner, survey, demo-session, linkedin-post, job-listing. Combo discount applies automatically."
    • removedInput schema / properties / oneoff_ids / items / enum
      Removed value: -[
-  "newsletter-section",
-  "newsletter-dedicated",
-  "meetup-hosted",
-  "podcast-episode",
-  "dinner",
-  "survey",
-  "demo-session",
-  "linkedin-post",
-  "job-listing"
-]
    • removedInput schema / properties / oneoff_ids / minItems
      Removed value: -1
    • changedInput schema / required
      Previous value: -[
-  "oneoff_ids",
-  "context"
-]New value: +[
+  "context"
+]
  6. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description still adds real context by clarifying this produces a 'decision-ready quote a human can sign' rather than executing a purchase (important given the name 'buy_reach'), and that budget_eur does not alter prices. It stops short of stating pricing semantics or whether quotes expire.

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-loaded with the question being answered, then the mechanics in one sentence. The nine-item enumeration makes it dense, but every clause conveys a distinct capability; a small trim of the item list would improve scannability.

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?

With an output schema present, return values needn't be described, and annotations cover the safety profile. The description still completes the picture by covering cart construction, discount application, and quote framing — everything needed to choose and call this tool 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?

Schema coverage is 100%, so baseline is 3; the description adds value beyond the schema by explaining the speaker-rung ladder ('from a meetup slot to the full coached programme'), the 30-word/link and no-jobs constraint on classifieds, and that combo discount applies automatically. It does not explain interactions between budget_eur and cart selection beyond the schema's own note.

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?

States a specific verb (builds a cart, applies the published combo discount) and resource (ELC's nine published one-off reach items, named exhaustively), and the front-loaded question it answers makes the intent unambiguous. No sibling tool does pricing/quoting, and the description makes that distinction evident.

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?

The framing question ('how do we get in front of 3,500+ CEE engineering leaders, and what does it cost?') implies when to call it, but there is no explicit when-not or routing against siblings like build_partnership_business_case or assess_community_launch_readiness, which an agent could plausibly confuse with a cost/business-case tool.

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

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

Resources