Skip to main content
Glama
coz-a

severally

by coz-a
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

List recent consultations

consult_list
Read-only

List recent consultations from earlier sessions, newest first, with IDs, status, summaries, verdicts, job IDs and remaining rounds; filter by target, question text or chain ID.

Instructions

Recent consultations, earlier sessions' too (this_session is false), newest first, with their ids, status, summary, verdicts, latest_completed_job_id and rounds_remaining. Optional target, question (case-insensitive substring), chain_id filters apply before limit. usage_totals is the tokens/cost reported this session, retries included. A figure a CLI does not report is named under not_reported, not counted as zero.

Input Schema

NameRequiredDescriptionDefault
limitNo
targetNo
chain_idNo
questionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.9.0
    • addedInput schema / properties / chain_id
      Added value: +{
+  "maxLength": 80,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / question
      Added value: +{
+  "maxLength": 4000,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / target
      Added value: +{
+  "maxLength": 120,
+  "minLength": 1,
+  "type": "string"
+}
  2. Changed1 schema field changedv1.4.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observedv1.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that: newest-first ordering, the exact field set returned, the fact that filters are applied before the limit, and the nuance that usage_totals includes retries while unreported figures appear under not_reported rather than as zero. It stops short of describing default limit behavior or the shape of a paginated/empty result.

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?

Front-loaded with what the tool returns, then filters, then the usage_totals caveat — a sensible ordering. Every sentence carries information, though the dense run-on phrasing around the filters and usage_totals requires a second read.

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 correctly takes on the job of enumerating return fields and their ordering, which it does well. Filter-vs-limit ordering and the not_reported convention round it out. The main residual gap is the unexplained 'target' filter, which matters for a tool with four optional parameters.

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 0%, so the description carries the full burden. It meaningfully explains 'question' as a case-insensitive substring filter, states that filters (target, question, chain_id) apply before limit, but leaves 'target' and 'chain_id' semantically opaque — an agent cannot tell what a target is or what a chain groups. Three of four parameters get some treatment, but the coverage gap is not fully compensated.

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 names a specific resource (recent consultations) and enumerates the returned fields (ids, status, summary, verdicts, latest_completed_job_id, rounds_remaining) plus ordering (newest first). The parenthetical '(this_session is false)' clarifies it spans earlier sessions, which implicitly distinguishes it from a single-session view. It never names a sibling tool like consult_get to draw the boundary explicitly, so it falls short of 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 Guidelines3/5

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

Usage is implied by the listing nature and by 'filters apply before limit', but there is no explicit statement of when to choose this over consult_get (single record) or consult_export. No when-not guidance and no prerequisites are given. An agent can infer the selection rule, but must infer it.

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