Skip to main content
Glama

Debian Security Advisories — buy per-query in-session (debianwatch)

data_session_query

Optional paid queries — competing is free. Listing: Debian Security Advisories at 0.01 USDC per query (max 20 queries/session). Sequence: data_session_open → data_session_funding_package (self-sign from buyer_address) → data_session_attach_escrow (open_tx_hash) → data_session_query.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>",
      "query": "<query>"
    },
    "name": "data_session_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
kNo
queryYes
session_idYesUUID of a data session you opened (from data_session_open).
sandbox_receiptNoLet the platform sign the DeliveryReceipt with your provisioned sandbox wallet — testnet sandbox wallets only.
delivery_receiptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior4/5

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

Annotations already declare the non-read-only, non-idempotent, non-destructive profile, and the description adds genuinely new behavior on top: a concrete cost (0.01 USDC per query) and a hard quota ceiling (max 20 queries/session), which matter for call planning. It still omits whether a failed query is charged, what happens at the quota limit, and what the call returns, but the economic and quota disclosure is substantive.

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?

It is short and the sequence is placed at the end where it is easy to follow, but the fragment style is terse to the point of ambiguity and the leading clause "Optional paid queries — competing is free" spends words without conveying actionable meaning. Price and quota are buried mid-sentence rather than front-loaded.

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?

This is a paid, non-idempotent operation with no output schema and only 40% parameter coverage, so the description needs to do more. It says nothing about the response shape, whether a delivery receipt is returned or required, how quota exhaustion or payment failure surfaces, or what the k parameter controls.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 40%, so the description carries a compensating burden that it does not meet. Only session_id is indirectly referenced (via the sequence), while query, k, sandbox_receipt, and delivery_receipt receive no explanation of expected content, sizing, or signing behavior. Names like "k" and "delivery_receipt" remain opaque.

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 speaks of "Optional paid queries" and a listing with a per-query price, which gestures at running a paid query, but it never states plainly that this tool executes a query against an already-funded session or what it returns. The most explicit statement of purpose ("Run a prepaid query against a funded data session") lives in the input schema, not the description. It is distinguishable from siblings only indirectly, via the sequence tail position.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The ordered chain data_session_open → data_session_funding_package → data_session_attach_escrow → data_session_query does convey the prerequisite state required before calling, which is real usage context. However, there are no explicit when-not conditions, no statement about what to do if the session lacks quota, and the phrase "competing is free" is unexplained and does not route the agent to any named alternative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources