Skip to main content
Glama
Sign In

Oceanir

by io.github.Oceanir
OverviewDiscussionsAdmin

Create an Oceanir case

create_case

Create an empty case to group related results. Free: it spends no credits. Returns the case id to pass to analyze_case_image.

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": {
      "name": "<name>"
    },
    "name": "create_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesA label you will recognise, for example the listing or claim it is about.
descriptionNoOptional context, such as the location the source claims.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare it is a non-readonly, non-destructive, non-idempotent, closed-world mutation. The description adds genuinely new behavior: it creates an *empty* case, it consumes no credits, and it returns a case id for downstream use. It does not restate the non-idempotency implication (repeated calls create separate cases), but the annotations carry that.

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?

Three short sentences, each earning its place: what it does, its cost profile, and what it returns. The purpose is front-loaded and nothing is redundant.

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?

For a two-parameter creation tool, the description covers purpose, cost, and the return value needed for the next step, compensating for the absent output schema. Nothing an agent needs in order to call it correctly and use the result 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% with both parameters fully documented, including examples and length limits, so the baseline is 3. The description contributes indirectly by calling the case 'empty', clarifying that name/description are the only inputs and no results are attached at creation time, but it adds no syntax or format detail beyond the schema.

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 ('Create an empty case') plus its purpose ('to group related results'), and the 'empty' qualifier distinguishes it from the analysis-producing siblings like analyze_case_image. An agent can identify this as the entry point of the workflow without opening any schema.

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 clear usage context: call it first to create a container, then pass the returned case id to analyze_case_image. It also notes the operation is free, which helps an agent decide against pre-checking check_credits. It stops short of stating exclusions, such as when to reuse an existing case via list_cases instead of creating a new one.

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