Skip to main content
Glama

Concierge Intel

by xyz.conc-exe
OverviewDiscussionsAdmin

intel_verdict

intel-verdict — $0.10 USDC/USDG/USDT x402 (or TCX credits). POST https://conc-exe.xyz/api/concierge-intel-verdict. Default body: {"message":"Solana DeFi outlook","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. First observed

TDQS

C2.6/5.0
Behavior3/5

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

The description discloses some behavior, such as payment requirements and the option to receive a payment challenge, but it does not describe what happens after a successful call, what data is returned, or what side effects occur beyond payment settlement.

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?

The description is relatively compact and includes necessary payment and endpoint details, though some repetition around payment methods could be tightened. The structure is acceptable for the information conveyed.

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 or description of the response format, making it unclear what the tool returns. The description also lacks context about the 'verdict' semantics, leaving significant gaps for an agent trying to determine expected results.

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?

All parameters are described in the schema, but the descriptions are minimal. For example, 'body' is described only as a JSON POST body for the route without explaining its fields, and 'paymentSignature' references 'x402 settlement' without clarifying the expected format beyond Base64.

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 does not clearly state what action the tool performs or what a 'verdict' means in this context. It mentions the endpoint, default body, and payment but omits the core function and return value, making it hard to distinguish from sibling intel_* tools.

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?

No guidance is provided about when to use this tool versus sibling tools like intel_macro, intel_wallet, or intel_whales. The description focuses on payment mechanics rather than usage context or selection criteria.

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