Skip to main content
Glama

Concierge Intel

by xyz.conc-exe
OverviewDiscussionsAdmin

intel_tvl

intel-tvl — $0.02 USDC/USDG/USDT x402 (or TCX credits). POST https://conc-exe.xyz/api/concierge-intel-tvl. Default body: {}. 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

D1.7/5.0
Behavior2/5

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

With no annotations, the description must carry behavioral disclosure. It does describe the payment/challenge flow and headers, but omits side effects, success return data, and whether the operation is read-only.

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 but jargon-heavy and confusing; payment details are relevant, but phrasing like 'live PAYMENT-REQUIRED accepts' and mixing currencies/chains without clear structure reduces clarity.

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

Completeness1/5

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

No output schema and no annotations; the description fails to explain the core function, success response, or how it fits with sibling tools, leaving the agent under-informed.

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 descriptions cover all 5 parameters at 100%, and the description adds little beyond restating the endpoint and payment options; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description never states what data or action the tool performs; it only mentions the endpoint, payment methods, and unpaid response behavior. 'intel-tvl' in the name implies TVL intelligence, but no verb or resource outcome is provided.

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 on when to use this tool versus sibling intel_* tools; no criteria, prerequisites, or alternative recommendations are given.

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