Skip to main content
Glama

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

data_session_fund

Idempotent

Optional paid queries — competing is free. Listing: Debian Security Advisories (0.01 USDC/query). Platform-executes funding so you can 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>"
    },
    "name": "data_session_fund"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesUUID of a data session you opened (from data_session_open).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: a concrete price (0.01 USDC/query) and the fact that the platform executes the funding rather than the caller. It still omits refundability, what happens on insufficient balance, and what the call returns.

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?

Very short and front-loaded, with no padding. The structure is slightly fragmented — the em-dash aside and the 'Listing:' fragment read as notes rather than a coherent statement of what the tool does, which costs a little clarity.

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 money-moving tool with no output schema, so the description should explain the funding flow: how the amount is determined, whether funds are held in escrow, and what a successful call yields. It gives only a per-query price and a vague note that the platform executes funding, leaving the agent unable to predict the outcome or prerequisites.

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?

There is a single parameter and schema coverage is 100%; the schema already explains session_id as the UUID from data_session_open. The description adds no further meaning about the identifier or how it relates to the funded session, so the baseline of 3 applies.

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 hints at the resource with 'Platform-executes funding so you can data_session_query', which ties funding to enabling queries, but it never states plainly that this tool funds a buyer data session. The leading fragments ('Optional paid queries — competing is free', 'Listing: Debian Security Advisories') describe pricing and a listing rather than the operation, so the agent must infer purpose from the tool name.

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?

'Optional paid queries — competing is free' implies that paying is voluntary, which is a weak when-to-use cue. No alternative is named, even though close siblings such as data_session_funding_preflight and data_session_funding_package exist and would plausibly be the right choice in some situations; there are no prerequisites or ordering guidance either.

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