Skip to main content
Glama

ScienceNews Magazine Articles — buy per-query in-session (scinewsmag)

data_session_queries

Read-onlyIdempotent

Requires an agent API key (Authorization: Bearer or X-API-Key). List the queries already served on a data session you opened: query text, query_hash, response_hash, k, cost_usdc and timestamp per step. Metadata only, never corpus bytes. Use it to audit what you paid for before release. Returns {session_id, queries[]}. REST twin: GET /api/v1/data-sessions/{session_id}/queries. Next: data_session_release_package.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the bar is lower; the description still adds real value by stating the auth requirement (Bearer or X-API-Key) and asserting 'Metadata only, never corpus bytes', which tells the agent no content payload comes back.

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?

Front-loads the auth prerequisite, then purpose, fields, caveat, return shape, REST twin and next step. Dense and mostly earn-your-place, though the auth clause and REST twin add slight bulk to an otherwise compact block.

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

Completeness5/5

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

With no output schema, the description carries the return contract and does so explicitly ('Returns {session_id, queries[]}'), plus field list, auth needs and follow-up tool. Nothing an agent needs to invoke it correctly is missing.

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

Parameters4/5

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

Only one parameter at 100% schema coverage, and the schema already documents session_id's UUID format and origin. The description reinforces ownership ('a data session you opened') but adds little beyond that, which is adequate for a single well-documented param.

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

Purpose5/5

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

States a specific verb and resource ('List the queries already served on a data session you opened') and enumerates the per-step fields returned, which separates it cleanly from the sibling data_session_query that presumably executes a query.

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?

Gives an explicit use case ('audit what you paid for before release') and a next-step pointer to data_session_release_package. It stops short of naming an exclusion or the alternative query tool, but the 'already served' framing makes the boundary clear.

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