Skip to main content
Glama

List Unknowns

list_unknowns
Read-onlyIdempotent

Lists current residual-unknown heads in deterministic ID order, with optional exact status, severity, and domain filters plus offset/limit paging to inspect unresolved, contradicted, or non-truth dispositions.

Instructions

List current residual-unknown heads in deterministic ID order, with optional exact status, severity, and domain filters. Results are complete inline by default; supply offset and limit to page the filtered order. total is the matching-head count and next_offset is null when the page exhausts the result. This is read-only; unresolved, contradicted, and non-truth dispositions remain distinct.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 50,
      "offset": 0
    },
    "name": "list_unknowns"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoOptional maximum number of heads to return. Omit to return every matching head from offset.
domainNo
offsetNoZero-based offset in the stable filtered unknown ID order.
statusNoCurrent lifecycle or verification status.
severityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only and idempotent, and the description reinforces that ('This is read-only') while adding behavior beyond them: stable ID ordering, complete-by-default results, total/next_offset paging semantics, and the note that unresolved, contradicted, and non-truth dispositions remain distinct. That last note is genuinely non-obvious behavior that no annotation conveys.

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 sentences ordered by importance: what it lists, how paging works, then semantics/safety. Every sentence carries information an agent needs, and nothing repeats the annotations verbatim.

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?

With no output schema, the description usefully explains the returned total and next_offset values and when next_offset is null, and it covers the default full-result behavior. The remaining gap is that 'residual-unknown head' and 'non-truth dispositions' are domain jargon left unexplained.

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 60%: offset and limit already have descriptions, but status, severity, and domain do not. The description compensates partially by calling them 'exact' filters and clarifying that offset operates on the stable filtered order, but it never gives value hints or explains how the filters combine. Baseline 3 fits.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List current residual-unknown heads') plus the ordering ('deterministic ID order') and available filters, so an agent can tell this apart from the generic list_* siblings. It stops short of naming any alternative, so it earns a 4 rather than a 5.

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 default ('Results are complete inline by default') and the condition for using paging ('supply offset and limit to page the filtered order'), which is the main usage decision for this tool. No explicit when-not-to-use or alternative tool is named, so a 4.

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

Deploy Server

Other Tools