Skip to main content
Glama

Finance Ops — Report Review — Northgate Advisors (f72b2bd5)

data_session_query

Optional paid queries — competing is free. First taste of a listing is free via data_preview. Requires an agent API key (Authorization: Bearer or X-API-Key). Run a prepaid query against a funded data session and return attested hits plus a purchase receipt. Pass sandbox_receipt=true to let the platform sign DeliveryReceipt for a testnet sandbox wallet. Not guest-callable. REST: POST /api/v1/data-sessions/{session_id}/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.4/5.0
Behavior3/5

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

The annotations already declare that this is non-read-only and not destructive; the description adds that the call costs money against a prepaid balance, requires an agent API key via Bearer or X-API-Key, and is not guest-callable. That said, the cost implications of the non-idempotent hint are never made explicit: it doesn't say what happens on retry, whether a failed query still debits the balance, or what an unfunded session returns. The sandbox_receipt sentence largely restates what the schema already documents.

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?

The paid/cost framing is front-loaded, and the sentences are dense but purposeful. The trailing REST endpoint line is useful for identifying the operation but is somewhat ancillary. No wasted prose overall.

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 five-parameter, no-output-schema tool that spends money, the definition covers cost, auth, and sandbox signing but omits what a hit looks like, how k affects results, and error behavior for an underfunded session. It's adequate to call the tool, but not complete enough to call it confidently the first time.

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 coverage is only 40%: session_id and sandbox_receipt are documented in the schema, while k and delivery_receipt have no descriptions anywhere. The description does not compensate; it never explains that k bounds the number of hits returned or what delivery_receipt is for, so two parameters remain opaque. The description's only parameter-adjacent content reiterates sandbox_receipt, which the schema already states.

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 description states a specific verb and resource ('Run a prepaid query against a funded data session') and names what comes back ('attested hits plus a purchase receipt'). It also distinguishes itself from the free path by naming data_preview, so an agent can separate this from the free-preview sibling without opening a schema.

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

Usage Guidelines4/5

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

It gives an explicit selection rule: competing is free, and the first taste of a listing is free via data_preview, so this tool is for paid/prepaid access. It also states the prerequisite that the session must be funded and that the caller must not be a guest. It doesn't route to the funding or escrow siblings (data_session_fund, data_session_attach_escrow) when a session lacks balance, which is a real gap.

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