Skip to main content
Glama

Concierge Intel

by xyz.conc-exe
OverviewDiscussionsAdmin

intel_desk_brief

intel-desk-brief — $0.25 USDC/USDG/USDT x402 (or TCX credits). POST https://conc-exe.xyz/api/concierge-intel-desk-brief. Default body: {"message":"morning desk brief","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.9/5.0
Behavior3/5

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

With no annotations, the description must disclose behavior. It does disclose that unpaid calls return a payment challenge and that payment is required, which is relevant. However, it doesn't describe what the tool returns, side effects, or operational details beyond payment, leaving a gap for a paid API call.

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 a single dense block combining pricing, endpoint, default body, and payment options. It is concise but poorly structured, with no breaks or clear separation of concerns, making it harder to parse quickly.

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?

For a paid API call with no output schema, the description is incomplete. It fails to explain what a 'desk brief' contains, what the response looks like, or what an agent should expect. This is a critical gap for an agent deciding whether to invoke it.

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 by explaining the default body, clarifying that paymentSignature can be omitted to get a payment challenge, and mentioning creditsWallet and soonHolderWallet as alternative payment paths. This exceeds the schema's basic parameter descriptions.

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

Purpose3/5

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

The description names the resource 'desk brief' and the endpoint, but does not clearly state what the tool does—e.g., 'retrieve a morning intelligence briefing.' It implies a daily summary but focuses on pricing and payment mechanics, leaving the actual function vague.

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 on when to use this tool versus the many sibling intel tools. It doesn't say 'use for a daily overview' or 'use when you need a consolidated briefing.' The agent must infer purpose from the name and default message.

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