Skip to main content
Glama

omniseek_curator_view

Read-only

Reads source-curation state without mutating it: view the admission queue, a candidate’s last evidence packet, or per-source audit facts and safety flags.

Instructions

Use WHEN running the source-curation protocol (judge the admission queue or a source audit); READ curator state: queue | packet | audit. Never mutates. Pick a view with what: what: "queue" (the admission backlog) | "packet" (the last evidence packet of a candidate, with the submitter's draft) | "audit" (per-source neutral audit facts and safety flags, no verdict). candidate_id: the candidate, for what="packet". state: filter for what="queue": new / probed / awaiting_verdict / admitted / watching / rejected / owner_review / redline_blocked / parked_p2 / error.

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

An unknown what returns an error listing the valid values; a candidate with no packet yet returns {error} or {state}. Protocol: the /curator skill. More: omniseek docs/TOOLS.md, omniseek_curator_view.

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

Input Schema

NameRequiredDescriptionDefault
whatYes
stateNo
candidate_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.3/5.0
Behavior4/5

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

The readOnlyHint=true annotation is reinforced rather than contradicted, and the description adds real behavior beyond it: an unknown `what` errors with the list of valid values, and a candidate with no packet returns {error} or {state}. It stops short of describing auth needs, volume, or the shape of a successful payload, so it is good but not exhaustive.

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?

The core is well front-loaded (trigger, read-only nature, view enumeration), but the trailing block about MCP config prefixes, ToolSearch, and doc/skill pointers is meta-instructional noise that does not help select or invoke the tool. Roughly a third of the text is boilerplate.

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 three-parameter read tool with no output schema, the definition covers every parameter, the invalid-input path, and the empty-packet edge case, and it points at the protocol skill and docs for deeper semantics. Only the shape of a successful non-error response is left unpinned.

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% and no schema enum exists, so the description does all the work — it defines each `what` view, pins `candidate_id` to what="packet", and enumerates all ten legal values for the `state` filter on what="queue". This is exactly the compensation the low coverage requires.

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 ('READ curator state') and enumerates the three views it can return (queue | packet | audit). 'Never mutates' plus the source-curation protocol framing makes it clearly distinguishable from a mutation-oriented sibling 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 an explicit trigger ('Use WHEN running the source-curation protocol — judge the admission queue or a source audit') and a hard boundary ('Never mutates'). It does not explicitly name the alternative tool to use when you need to act, so the when-not side is only implied by the read-only constraint.

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