Marine buoy weather observations (marinewatch)

data_session_open

Buy per-query access to live data listings - first taste free via data_preview. Listing: marinewatch: Live NOAA marine buoy observations (0.01 USDC/query (max 20 queries/session)). Open a prepaid session, then fund and query.

Input Schema

TableJSON Schema

Name	Required	Description
`listing_id`	No	UUID of the listing. Provide exactly one of listing_slug or listing_id.
`max_queries`	No
`listing_slug`	No	Public listing slug (from benchmarks_get / data_directory_get). Provide exactly one of listing_slug or listing_id.
`open_tx_hash`	No
`buyer_address`	No	Buyer EVM address. Optional: defaults to your own platform wallet when omitted.
`proof_escrow_id`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed13 schema fields changedSep 7, 2026

addedInput schema / description

Added value: +"MCP-only input for ``data_session_open``.\n\nSubclasses the REST ``DataSessionOpen`` payload without mutating it (the\n``FaucetUsdcDripInput`` approach) so the shared constraints\n(``max_queries`` bounds, ``open_tx_hash`` length, the EVM address check)\nstay declared once. Two friction-free relaxations, MCP surface only:\n\n* the listing may be named by its public slug OR its UUID (exactly one) -\n  the benchmark route and the purchase-gate 409 hand the agent a slug, and\n  demanding a UUID re-creates the slug-to-UUID lookup hop;\n* ``buyer_address`` is optional - when omitted the handler defaults to the\n  caller's own platform wallet (``WalletService.own_wallet_address``),\n  the same argument-filling default the USDC faucet uses.\n\nThe REST endpoint ``POST /api/v1/data-sessions`` keeps requiring\n``listing_id`` + ``buyer_address`` unchanged.\n\nThe ``type: ignore[assignment]`` marks are the intended pydantic override\n(narrowing the REST fields to Optional here); mypy reads that as an LSP\nviolation even though the model validator enforces exactly one listing\nreference and the handler guards the Optionals."

addedInput schema / properties / buyer_address / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / buyer_address / default
```
Added value: +null
```

addedInput schema / properties / buyer_address / description

Added value: +"Buyer EVM address. Optional: defaults to your own platform wallet when omitted."

removedInput schema / properties / buyer_address / type
```
Removed value: -"string"
```

addedInput schema / properties / listing_id / anyOf

Added value: +[
+  {
+    "format": "uuid",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / listing_id / default
```
Added value: +null
```

addedInput schema / properties / listing_id / description

Added value: +"UUID of the listing. Provide exactly one of listing_slug or listing_id."

removedInput schema / properties / listing_id / format
```
Removed value: -"uuid"
```
removedInput schema / properties / listing_id / type
```
Removed value: -"string"
```

addedInput schema / properties / listing_slug

Added value: +{
+  "anyOf": [
+    {
+      "minLength": 1,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Public listing slug (from benchmarks_get / data_directory_get). Provide exactly one of listing_slug or listing_id.",
+  "title": "Listing Slug"
+}

removedInput schema / required

Removed value: -[
-  "listing_id",
-  "buyer_address"
-]

changedInput schema / title

Previous value: -"DataSessionOpen"New value: +"DataSessionOpenInput"

First observedSep 6, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations are all-false hints (readOnlyHint=false, idempotentHint=false, etc.) so they carry no safety-profile information and the description bears the full burden. The description does disclose the commercial nature (prepaid purchase, 0.01 USDC/query, 20-query session cap) and the open→fund→query ordering. But it omits meaningful behavioral context: the on-chain transaction implied by open_tx_hash, when proof_escrow_id is required, and what the call returns — significant gaps for a state-changing purchase tool.

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 purpose front-loaded and the data_preview alternative stated early. The embedded listing-specific pricing block is potentially useful if marinewatch is the only listing, but it is catalog content that could reasonably live outside the tool definition; otherwise the text is economical and earns its place.

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 6-parameter purchase tool with no output schema and minimal annotations, the definition conveys the basic flow (preview free → open → fund → query) and the schema covers the slug/UUID and buyer_address relaxations. Missing are the invocation-critical details an agent needs: what the tool returns (the session identifier presumably required by fund/query), when open_tx_hash or proof_escrow_id must be supplied, and failure behavior. These gaps make the definition adequate but not complete.

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 exactly 50% (listing_id, listing_slug, buyer_address have descriptions; max_queries, open_tx_hash, proof_escrow_id do not). The schema-level description compensates well by explaining the 'exactly one of slug or UUID' rule and the buyer_address wallet default. The tool description adds only pricing and session-cap context and does not clarify open_tx_hash or proof_escrow_id; additionally, its 'max 20 queries/session' sits awkwardly against the schema's max_queries ceiling of 50, which could confuse an agent.

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 action — 'Buy per-query access to live data listings... Open a prepaid session' — which aligns with the tool name and the annotation title 'Open Data Session'. It also distinguishes from siblings by positioning itself as the first lifecycle step ('then fund and query') and naming data_preview as the free alternative. However, the middle sentence reads as a catalog pitch for a single listing ('marinewatch: Live NOAA marine buoy observations (0.01 USDC/query)'), which narrows the general scope and slightly muddles the purpose.

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?

'First taste free via data_preview' is an explicit alternative for the trial use-case, and 'Open a prepaid session, then fund and query' clearly positions this tool as the required first step, implicitly excluding data_session_fund and data_session_query for the opening action. It falls short of a 5 because there is no explicit when-not-to-use phrasing and no mention of the attach_escrow/funding_package siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Marine buoy weather observations (marinewatch) tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?