Skip to main content
Glama
Sign In

Oceanir

by io.github.Oceanir
OverviewDiscussionsAdmin

List past Oceanir results

list_analyses
Read-onlyIdempotent

List this account's past Oceanir results, newest first: place, coordinates, confidence, depth and date. Read-only: it never runs a new analysis and never spends credits. Use it to find an earlier result instead of analyzing the same image again. Accounts with analysis history switched off return nothing. Reads the scene only (architecture, signage, terrain, vegetation), never the people in it. No face recognition, no biometric identification, no person matching. It answers where an image was taken, never who is in it, and must not be used to locate or track a person.

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": "list_analyses"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoOptional exact city name to filter by.
limitNoHow many results to return, newest first.
queryNoOptional text to match against the neighborhood, city or file name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already cover read-only and idempotency, yet the description adds credit-cost behavior ("never spends credits"), ordering (newest first), the empty-result case for disabled history, and a detailed privacy boundary about scene-only reading. This is materially more than the annotations provide.

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

Conciseness3/5

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

Front-loaded with the core purpose and return fields, which is good, but the privacy disclaimer is restated across three sentences ("never the people in it," "no face recognition, no biometric identification, no person matching," "where an image was taken, never who is in it"). That redundancy dilutes an otherwise tight definition.

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

Completeness4/5

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

For a read-only list tool with full schema coverage and no output schema, this covers returns, ordering, credit behavior, and the empty case adequately. Minor gaps remain around pagination beyond the limit cap and how filters combine, but nothing essential to correct invocation is missing.

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 coverage is 100%, so the schema already documents city, query, and limit. The description adds only the newest-first ordering context and confirms account scoping, without clarifying filter interaction (e.g., city vs. query) beyond what the schema states; baseline 3 is correct.

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 this account's past Oceanir results") and enumerates the returned fields: place, coordinates, confidence, depth, date. It also implicitly separates itself from the analysis siblings by framing the use case as "instead of analyzing the same image again."

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 a clear when-to-use case ("find an earlier result instead of analyzing the same image again") and an edge condition (accounts with history disabled return nothing). It does not name the specific alternatives (geolocate_image, analyze_case_image) or state exclusions by tool name, so it stops short of 5.

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