Skip to main content
Glama

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

data_session_open

Optional paid queries — competing is free. Listing: Debian Security Advisories (0.01 USDC/query (max 20 queries/session)). Open a prepaid session, then fund and query.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "data_session_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
listing_idNoUUID of the listing. Provide exactly one of listing_slug or listing_id.
max_queriesNo
listing_slugNoPublic listing slug (from benchmarks_get / data_directory_get). Provide exactly one of listing_slug or listing_id.
open_tx_hashNo
buyer_addressNoBuyer EVM address. Optional: defaults to your own platform wallet when omitted.
proof_escrow_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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=false and openWorldHint=false, so the safety profile is covered structurally. The description adds genuinely useful economics (0.01 USDC/query, capped at 20 queries per session) that annotations cannot express, but it omits what a session object contains, what happens on repeat opens, and what the escrow/proof parameters imply behaviorally.

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?

Three short sentences with the actionable instruction front-loaded in the last clause and the price/limit facts compactly parenthesised. The 'competing is free' fragment and the single-listing callout are marginally wasteful but do not impede parsing.

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 six-parameter, zero-required session-creation tool with no output schema and no annotations explaining lifecycle. The description should say what an opened session yields and how escrow/proof parameters relate to it; instead it stops at 'fund and query', leaving the highest-risk parameters undocumented in both description and schema.

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 description coverage is 50%, and the schema itself already explains listing_slug vs listing_id and the buyer_address default. The description contributes the max-20-queries convention that maps to max_queries (whose schema maximum is 50), but leaves open_tx_hash, proof_escrow_id and the required 'exactly one listing reference' rule entirely to the schema.

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

Purpose4/5

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

The final sentence states a specific verb and resource: 'Open a prepaid session, then fund and query', which tells an agent this is the entry point of a multi-step purchase flow rather than a funding or querying call. The opening fragments ('Optional paid queries — competing is free') and the single hard-coded listing example add noise that slightly obscures the core action.

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?

'Open a prepaid session, then fund and query' implies sequence relative to the sibling funding and query tools, so an agent can infer this comes first. However, there is no explicit when-not guidance, no statement of prerequisites (e.g. wallet balance, existing session), and no named alternative for agents that only want to preview data.

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