Skip to main content
Glama
vighriday

Veris

by vighriday
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

confidence_history

Fetch verification-coverage and execution-depth metrics from recent runs, with an optional limit. Handles disabled persistence by returning an empty trend.

Instructions

Returns verification-coverage and execution-depth values across recent runs recorded in .veris/state.db, newest first. Defaults to 30 runs, capped at 100. Returns an empty trend with stateEnabled:false when persistence is disabled (VERIS_STATE_DISABLED=1).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum runs to return. Default 30, maximum 100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.1
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of runs to return. Defaults to 20."New value: +"Maximum runs to return. Default 30, maximum 100."
  2. Changed1 schema field changedv0.1.0
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of runs to return. Defaults to 20."
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden. It transparently describes what is returned, the default and maximum number of runs, and the special empty-trend behavior when persistence is disabled. It does not mention side effects, but the read-only nature is strongly implied.

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 concise and well-structured, using three short sentences that each convey a distinct piece of information: the primary output, the default/cap, and the disabled-persistence behavior. There is no redundant or irrelevant content.

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?

The description is complete for a simple retrieval tool: it specifies the data returned, ordering, default and maximum limits, and behavior when persistence is disabled. It does not describe an output schema, but none is provided and the return concept is clear enough for likely use cases.

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?

The schema already fully describes the limit parameter with default and maximum values, and the description largely repeats this information. Since schema coverage is 100%, the baseline is 3, and the description adds no additional semantic detail beyond the schema.

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?

The description clearly states that the tool returns verification-coverage and execution-depth values across recent runs, which is specific and action-oriented. It does not explicitly name or contrast sibling tools, but the resource and scope are distinctive enough to infer its purpose.

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

Usage Guidelines3/5

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

It provides useful context about default limits, maximum limits, and disabled-persistence behavior, but it does not explicitly state when to use this tool versus alternatives like node_history or report_execution. The guidance is implied rather than explicit.

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