Skip to main content
Glama

Concierge Intel

by xyz.conc-exe
OverviewDiscussionsAdmin

intel_momentum

intel-momentum — $0.10 USDC/USDG/USDT x402 (or TCX credits). POST https://conc-exe.xyz/api/concierge-intel-momentum. Default body: {"theme":"robinhood","message":"Robinhood Chain meme rotation — CASHCAT and Pump.fun cross-chain","limit":5,"includeInsider":true}. Unpaid calls return live PAYMENT-REQUIRED accepts (Solana/Base/Arbitrum USDC · Robinhood USDG · BNB USDT/USDC Permit2).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoJSON POST body for the intel/security route
agentIdNoOptional Concierge agent id (agt_…)
creditsWalletNoSolana wallet for TCX prepaid credits (x-tcx-credits-wallet)
paymentSignatureNoBase64 PAYMENT-SIGNATURE after x402 settlement. Omit to receive a structured payment challenge (or settle via creditsWallet / SOON holder headers).
soonHolderWalletNoSolana wallet for SOON/TCX holder free tier (X-Soon-Holder-Wallet)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / agentId
      Added value: +{
+  "description": "Optional Concierge agent id (agt_…)",
+  "type": "string"
+}
    • changedInput schema / properties / body / description
      Previous value: -"JSON POST body"New value: +"JSON POST body for the intel/security route"
    • addedInput schema / properties / creditsWallet
      Added value: +{
+  "description": "Solana wallet for TCX prepaid credits (x-tcx-credits-wallet)",
+  "type": "string"
+}
    • changedInput schema / properties / paymentSignature / description
      Previous value: -"Base64 PAYMENT-SIGNATURE header after x402 settlement"New value: +"Base64 PAYMENT-SIGNATURE after x402 settlement. Omit to receive a structured payment challenge (or settle via creditsWallet / SOON holder headers)."
    • addedInput schema / properties / soonHolderWallet
      Added value: +{
+  "description": "Solana wallet for SOON/TCX holder free tier (X-Soon-Holder-Wallet)",
+  "type": "string"
+}
  2. Changed4 schema fields changed
    • addedInput schema / properties / body / default / includeInsider
      Added value: +true
    • addedInput schema / properties / body / default / limit
      Added value: +5
    • addedInput schema / properties / body / default / message
      Added value: +"Robinhood Chain meme rotation — CASHCAT and Pump.fun cross-chain"
    • addedInput schema / properties / body / default / theme
      Added value: +"robinhood"
  3. First observed

TDQS

C2.4/5.0
Behavior3/5

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

With no annotations, the description does disclose some behavior: it mentions the payment requirement, credit options, and that unpaid calls receive a PAYMENT-REQUIRED challenge. However, it does not state whether the tool is read-only, what side effects occur, or what a successful call returns.

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

Conciseness3/5

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

The description is compact and includes the essential payment and endpoint details, but it is a dense run-on with mixed concerns (pricing, endpoint, default body, unpaid behavior). It could be better organized into separate sentences or sections.

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

Completeness2/5

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

There is no output schema and the description does not explain what a successful response contains or how the momentum intel is presented. Payment edge cases are covered, but the core deliverable of the tool is left undefined.

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?

All five parameters have descriptions, and most are meaningful (agentId, creditsWallet, paymentSignature, soonHolderWallet). The body parameter is only generically described as 'JSON POST body', and its inner fields are not individually documented, so a little clarity is lost.

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 identifies the tool as 'intel-momentum' and gives an endpoint and default body, but never explicitly states what momentum intelligence is retrieved or what the caller should expect. The purpose is implied by the name and default message rather than clearly defined.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 this tool instead of the many sibling intel tools. It explains payment mechanics but not the intended use case or selection criteria relative to alternatives like intel_macro or intel_scalp.

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

All Concierge Intel 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