Skip to main content
Glama

Concierge Intel

by xyz.conc-exe
OverviewDiscussionsAdmin

intel_listing

intel-listing — $0.10 USDC/USDG/USDT x402 (or TCX credits). POST https://conc-exe.xyz/api/concierge-intel-listing. Default body: {"message":"Potential exchange listings","limit":5}. 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. Changed7 schema fields changed
    • addedInput schema / properties / agentId
      Added value: +{
+  "description": "Optional Concierge agent id (agt_…)",
+  "type": "string"
+}
    • addedInput schema / properties / body / default / limit
      Added value: +5
    • addedInput schema / properties / body / default / message
      Added value: +"Potential exchange listings"
    • 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.2/5.0
Behavior3/5

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

With no annotations, the description carries the transparency burden. It does disclose the payment requirement, cost, and 402 response for unpaid calls, and mentions a free tier via SOON holder headers. However, it does not explicitly state side effects or whether the operation is read-only, though the intel namespace suggests a non-destructive query.

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

Conciseness2/5

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

The description is dense and mixes cost, endpoint, default body, and payment variants in a single run-on style without a clear lead purpose statement. It is not excessively long but lacks a clear structure and front-loaded intent.

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 specify what a successful response contains. It only describes the default request body and payment-failure behavior, leaving the actual returned data and success criteria undefined.

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?

The schema descriptions cover all 5 parameters, including paymentSignature behavior and wallet header mappings. The tool description adds no extra parameter context beyond what the schema already provides, so the baseline score of 3 applies.

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 focuses on payment mechanics, endpoint URL, and default body rather than clearly stating what the tool does. The phrase 'Potential exchange listings' in the default body hints at the purpose, but the actual function and output are not explicitly described.

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?

No guidance is provided on when to use this tool versus sibling intel_* tools, nor when to choose paymentSignature, creditsWallet, or soonHolderWallet. The description only conveys payment mechanics, not use cases or alternatives.

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