Skip to main content
Glama

omniseek_statement

Record, list, or retract typed relation statements in the graph when a decision-relevant relation is not already stored mechanically, with required reasoning notes and optional provenance.

Instructions

Use WHEN you've concluded a DIRECTED, decision-relevant relation OmniSeek does NOT already store mechanically (X acquired_by Y, paper P refutes claim Q, path R requires gate S) and want the graph to carry it forward: record / list / retract typed relation statements (the general sibling of omniseek_ruling; identity types belong to omniseek_ruling).

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

Record one only when all three hold: OmniSeek does not already store it (cites, authored, affiliated and the like are mechanical), it would change a future decision, and a point-in-time relation carries its as-of date in the note. Prose conclusions belong in notes, not here. create (src, dst, type, note; optional doc): type is free vocabulary, slugged to [a-z0-9_], at most 40 characters; note (your reasoning) is required; doc is a provenance node id. Returns {created, statement, replaced, similar_anchors?}: reuse a hand-minted id from similar_anchors instead of minting a near-duplicate. (src, dst, type) is the key; re-creating replaces it. list (optional about, type): {statements, count}, at most 200 (capped flag). delete (src, dst, type): {deleted}. Shown by omniseek_graph under working and exploratory, and on later omniseek_search hits of an endpoint. Refused with {error}: type same_as / not_same_as (use omniseek_ruling), a bad type, an empty endpoint or note, an unknown action. More: omniseek docs/TOOLS.md, omniseek_statement.

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_statement"
  }
}

Input Schema

NameRequiredDescriptionDefault
docNo
dstNo
srcNo
noteNo
typeNo
aboutNo
actionYes

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 supply readOnlyHint=false, so the description carries the burden and does: it discloses return payloads for all three actions ({created, statement, replaced, similar_anchors?}, {statements, count} capped at 200, {deleted}), the replace-on-key behavior for (src, dst, type), the similarity-reuse hint, and the exact refusal cases. It also states where results surface downstream (omniseek_graph, omniseek_search).

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?

The WHEN clause is front-loaded and the per-action bullets are dense and scannable with zero filler in the body. The self-referential block about MCP prefixes and ToolSearch consumes several lines and describes client plumbing rather than the tool's behavior, which is the main thing that does not earn its place.

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 7-parameter, no-output-schema mutation tool this is unusually complete: return shapes, caps, replace semantics, and refusal modes are all documented. The remaining gaps are minor but real — `about` is unexplained and the cap behavior of list (the `capped` flag) is mentioned without saying what the caller should do about it.

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?

Schema coverage is 0%, so the description must compensate, and it largely does: type is defined as free vocabulary slugged to [a-z0-9_] with a 40-character cap, note is marked required reasoning, and doc is identified as a provenance node id. However, `about` is listed for list with no explanation of what it filters on, and src/dst are only implied by the examples rather than defined.

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 description names the exact verb set (record / list / retract) and resource (typed relation statements) and explicitly positions itself as the general sibling of omniseek_ruling, with identity types routed elsewhere. The parenthetical examples (X acquired_by Y, paper P refutes claim Q, path R requires gate S) make the resource concrete rather than abstract.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit WHEN clause plus three conjunctive conditions for recording (not already stored mechanically, decision-relevant, carries an as-of date), names the alternative tool for identity types (omniseek_ruling), and redirects prose conclusions to notes. The exclusions are as clear as the inclusions, which is rare.

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