Skip to main content
Glama

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

data_session_funding_package

Read-onlyIdempotent

Optional paid queries — competing is free. Listing: Debian Security Advisories (0.01 USDC/query). Returns fund instructions after data_session_open.

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_funding_package"
  }
}

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

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. Beyond that, the description adds real behavioral context the annotations lack: the operation is optional/paid, a price point (0.01 USDC/query) applies, and the tool returns instructions rather than moving funds — clarifying it does not mutate balances despite the 'funding' name.

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, but the structure is disjointed: three fragments where the leading commercial/listing sentence carries the least operational value and pushes the actual behavior ('Returns fund instructions') to the end. Front-loading the return behavior would make it materially clearer.

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

Completeness3/5

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

For a one-parameter tool with no output schema, the description should at minimum characterize what the fund instructions contain and where the agent goes next; it names the prerequisite but not the follow-on (e.g., data_session_fund) nor the shape of the returned instructions. Adequate to attempt a call with a valid session_id, but thin on what happens after.

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 with 100% schema description coverage; the schema already explains that session_id is the UUID from data_session_open. The description reinforces the data_session_open dependency but adds no format or sourcing detail beyond the schema, so the baseline 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 operative sentence, 'Returns fund instructions after data_session_open,' states a reasonably specific effect, but it is buried behind marketing framing ('Optional paid queries — competing is free') and a listing blurb ('Listing: Debian Security Advisories (0.01 USDC/query)') that reads as catalog copy rather than tool purpose. An agent must infer that this tool produces payment/funding instructions for a session rather than performing the funding itself.

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?

'after data_session_open' gives an implied ordering constraint, which is genuine sequencing guidance. However, there is no explicit statement of when to choose this over the obvious siblings data_session_funding_preflight or data_session_fund, and no when-not guidance at all.

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