Skip to main content
Glama

Physics & Technology News — buy per-query in-session (physorgwatch)

data_session_funding_package

Read-onlyIdempotent

Optional paid queries — competing is free. Listing: physorgwatch: Physics & Technology News (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

C2.9/5.0
Behavior3/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. The description adds one genuinely useful behavioral fact — this returns fund *instructions* rather than moving funds, which is important next to data_session_fund — but says nothing about what the instructions contain, whether they expire, or what the caller must do with them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Only two sentences, but the first is a dash-joined fragment mixing positioning copy with a hardcoded listing name and price, which reads as noise in a tool definition. The actual operative information (returns fund instructions, call after open) is buried in the second sentence.

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, read-only, no-output-schema tool, stating the prerequisite and the rough nature of the return is close to sufficient. However, the stray listing/price fragment raises unanswered questions (is a listing selected here? is a price accepted?) that the description never resolves.

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, including the UUID format and the note that it comes from data_session_open. The description adds no meaning beyond that; notably it never mentions session_id, so it does not compensate for anything nor risk contradicting the schema.

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 name implies a funding package for a data session, and the closing clause 'Returns fund instructions after data_session_open' is the only part that actually states the verb and resource. The opening clause 'Optional paid queries — competing is free' and the inline listing/price example pull focus toward marketing rather than stating what the tool produces, and it does not clearly separate itself from data_session_funding_preflight or data_session_fund.

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?

'Returns fund instructions after data_session_open' establishes an implied prerequisite ordering, and 'Optional paid queries' hints that it is only relevant when the buyer chooses to pay. There is no explicit when-not guidance and no naming of the preflight or fund siblings that an agent would otherwise have to disambiguate between.

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