Skip to main content
Glama
Sign In

Oceanir

by io.github.Oceanir
OverviewDiscussionsAdmin

Check Oceanir usage

get_usage
Read-onlyIdempotent

Read the last 30 days of Oceanir usage for the authenticated account: calls, credits used, a breakdown by depth, and what remains. Read-only; it never spends credits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the 'Read-only' restatement adds little, but 'it never spends credits' tells the agent calling it has no cost side effect, and the fixed 30-day window is behavioral context not present in annotations. No pagination or response-shape detail, which is acceptable for a fixed small report.

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

Conciseness5/5

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

Two sentences, front-loaded with the scope and resource, then the return contents, then the safety note. No filler and nothing repeated.

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 input parameters and no output schema, the description compensates by enumerating exactly what the response contains and fixing the time window. An agent has everything needed to call it and interpret the result.

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?

The tool takes zero parameters, so the schema carries the full burden and the baseline is 4. The description correctly adds no parameter talk, keeping the implied no-argument contract unambiguous.

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?

Specific verb+resource ('Read the last 30 days of Oceanir usage'), scoped to the authenticated account, and it enumerates what is returned (calls, credits used, breakdown by depth, remaining balance). It does not explicitly distinguish itself from the sibling check_credits, whose territory 'what remains' partially overlaps.

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?

The 30-day window implies when this tool is appropriate - historical consumption review - but there is no explicit statement of when to prefer check_credits or any other sibling, and no exclusions. Usage is inferable rather than stated.

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

All Oceanir toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources