Skip to main content
Glama
Sign In
severally

severally

by coz-a
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

List recent consultations

consult_list
Read-only

Lists recent and earlier consultations newest first, showing IDs, status, summaries, verdicts, remaining rounds, and usage totals; filter by target, question substring, 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. Pass filters at the top level, not in request. 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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "consult_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
targetNo
chain_idNo
questionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.12.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. 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"
+}
  3. 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"
  4. First observedv1.1.0

TDQS

A3.8/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, and the description adds real behavioral detail beyond that: filtering happens before limit is applied, results are newest-first and span earlier sessions, and usage_totals counts retries while unreported CLI figures are surfaced under not_reported rather than zeroed. It stops short of describing pagination behavior for limits.

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?

Dense, front-loaded and waste-free: return shape, scope, ordering, and filter behavior come first, then the top-level filter instruction, then the usage_totals/not_reported caveat. No sentence restates the title or the annotations.

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 takes on the job of naming the returned fields (ids, status, summary, verdicts, latest_completed_job_id, rounds_remaining) and explaining the usage_totals and not_reported accounting, which it does. The remaining gap is that 'target' and pagination behavior are not explained for an agent that has zero schema documentation.

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 must carry the load. It clarifies that question is a case-insensitive substring match and that target, question, and chain_id are pre-limit filters passed at top level, but 'target' is never explained and limit semantics beyond ordering are left to the schema's min/max.

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 states the resource (consultations), the ordering (newest first), the scope note that earlier sessions are included when this_session is false, and enumerates the returned fields. It is specific enough to distinguish a list operation from consult_get, though the verb 'list' is only implied and no sibling is named.

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 context is implied — filtering recent consultations — and there is a concrete instruction that filters must be passed at the top level rather than inside 'request'. However, nothing says when to choose this over consult_get or consult_export, and there are no exclusions or prerequisites.

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