Cortex

Listverifications

listVerifications

List verifications across the catalog, one entry per entity and verification period, including entities nobody has verified yet. Each entry names the entity, the period it belongs to, the status (PENDING, VERIFIED_CORRECT, VERIFIED_INCORRECT), and who verified it. Filter by periodCid, status, or isActive=true for periods that are open today. Use this to answer who still owes a verification, and which entities were reported incorrect.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	Yes	Page number to return, 0-indexed. Default 0.
`status`	No	Return only verifications in this state
`context`	Yes	Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your overall objective and fits into your broader plan across all tool calls (e.g., why this tool vs. others, and what step it unblocks). Never share any personal details or sensitive information.
`isActive`	No	Return only verifications whose period is open today (true) or only those whose period is not (false). Omit for all periods.
`pageSize`	Yes	Number of results to return per page, between 1 and 1000. Default 250.
`periodCid`	No	Return only verifications belonging to this verification period
`session_id`	Yes	Session continuity handle, one of two values: the ses_ ID issued for the task underway, or start. This server cannot link your calls between requests on its own, so session continuity travels in this parameter instead. If you were handed a session_id for this task — for example by the agent that spawned you — send that exact value from your first call. Otherwise send start on your first call; the server will issue an opaque correlation ID in the mcp_session field of the result, or in a text block at the start of the result beginning [session_id issued. Then send that exact ses_ value on every later call and hand it to any subagents working the same task. start always begins a new, unrelated task — never send it mid-task. If you send a value this server does not recognize, the result reports it: mcp_session.status of unrecognized, or a text block beginning [session_id unrecognized; re-send the ID issued for this task, or start if none was issued yet. Never invent a ses_ value.

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 25, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the behavioral disclosure burden. It explains the result shape (entity, period, status, verifier), the inclusion of unverified entities, and the available filtering scopes. This is transparent for a read-oriented listing tool, though it does not mention pagination behavior or whether verifier fields are null for unverified entries.

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?

The description is compact and front-loaded: it states what the tool lists, characterizes the result rows, notes the key unverified-entity behavior, summarizes filters, and gives a concrete use case. Every sentence adds value; there is no filler or redundancy.

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 tool with no output schema and no annotations, the description is reasonably complete: it defines the output granularity, the status values, the inclusion of unverified entities, and the main filters. It could be slightly stronger by pointing to listVerificationsForEntity for per-entity queries, but it does not leave a critical gap for selecting or invoking the tool.

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 description coverage is 100%, so the baseline is 3. The description reinforces the meaning of filters like status and isActive, and clarifies the purpose of the output, but it does not add significant parameter-level detail beyond what the schema already provides.

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 uses a specific verb ('List') and resource ('verifications across the catalog'), defines the unit of output ('one entry per entity and verification period'), and calls out a distinguishing feature ('including entities nobody has verified yet'). This clearly separates it from sibling tools like listVerificationsForEntity or listVerificationPeriods.

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?

The description gives clear application context: 'Use this to answer who still owes a verification, and which entities were reported incorrect.' It also explains when filters like periodCid, status, and isActive are relevant. It does not explicitly name alternatives or state when not to use this tool, but the guidance is concrete enough to route an agent appropriately.

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

All Cortex tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?