Skip to main content
Glama

omniseek_ruling

Record, list, or retract same-as/not-same-as rulings to tell graph views when two nodes represent the same person or entity, so they can collapse them.

Instructions

Use WHEN two graph nodes ARE (or are NOT) the same person / entity and you want views to collapse them: record / list / retract same_as | not_same_as rulings (the one judgment channel the graph's working policy applies).

Tool name: omniseek_ruling (your MCP config adds its own prefix; never guess one). Not in your tool list? ToolSearch "omniseek_ruling".

create (src, dst, verdict "same" | "not_same"; optional note): returns {created, ruling, replaced}; the unordered pair is the key, so re-creating replaces it. list: {rulings: [{src, dst, verdict, note, ruled_at}], count}. delete (src, dst): {deleted}. omniseek_graph applies rulings under its working and exploratory policies; not_same beats same. A bad verdict, empty or identical endpoints, or an unknown action return {error}. More: omniseek docs/TOOLS.md, omniseek_ruling.

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

Input Schema

NameRequiredDescriptionDefault
dstNo
srcNo
noteNo
actionYes
verdictNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false; the description goes well beyond that by documenting per-action return payloads ({created, ruling, replaced}, {rulings, count}, {deleted}), the key semantics (unordered pair, re-create replaces), the precedence rule (not_same beats same), and the error cases (bad verdict, empty or identical endpoints, unknown action). That is exactly the behavior an agent needs before mutating shared graph policy.

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?

Front-loads the use condition, then switches to a compact per-action bullet block, which is easy to scan. The middle boilerplate about MCP config prefixes and ToolSearch recovery does not help an agent decide or invoke and dilutes the otherwise tight text.

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 5-parameter mutating tool with no output schema, the description covers action modes, inputs, return values, precedence, and failure modes. Nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description has to carry the load, and it does: action values (create/list/delete), verdict domain ("same" | "not" | "not_same"), src/dst as unordered pair endpoints with empty/identical rejected, and note as optional. Little is left undocumented short of format specifics for node identifiers.

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?

The opening sentence names a specific verb family (record / list / retract) and a specific resource (same_as | not_same_as rulings over graph node pairs), and frames the effect on downstream views (collapse them). It also distinguishes the tool from omniseek_graph, which consumes rather than creates rulings.

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?

It gives an explicit trigger condition: use when two graph nodes are (or are not) the same entity and you want views to collapse them. It also notes that omniseek_graph applies these rulings under its working and exploratory policies and that not_same beats same, which is real context for choosing this tool. It stops short of stating when NOT to use it or naming a competing alternative.

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