Elicitly Pro

List past elicitations

elicit_history

Read-only

List your past elicitations, newest first, paginated with jump-to-page. scope 'me' = your own requests; 'org' = the whole organization (admins only). Returns { items, page, pageSize, asOf, total, scope } — total lets you compute the last page (ceil(total/pageSize)); pass the returned asOf back on later pages to keep the window stable while new requests arrive.

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": "elicit_history"
  }
}

Input Schema

Name	Required	Description	Default
`asOf`	No	Snapshot anchor from a previous page's result — pass it back to keep pagination stable while new requests arrive. Omit on the first page.
`page`	No	1-based page number to fetch.
`scope`	No	'me' = your own requests; 'org' = the whole organization (admins only).	me
`pageSize`	No	Items per page (1-100).

Output Schema

Name	Required	Description
`asOf`	Yes	The snapshot anchor this page was computed at — pass it back on later pages to keep the window stable while new requests arrive.
`page`	Yes	The 1-based page that was served.
`items`	Yes	The requested page of elicitations, newest first.
`scope`	Yes	The scope that was served.
`total`	Yes	Total matching requests — the last page is ceil(total / pageSize).
`pageSize`	Yes	Items per page that was applied.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 8, 2026
- changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```

Changed5 schema fields changedSep 5, 2026

addedInput schema / properties / asOf / description

Added value: +"Snapshot anchor from a previous page's result — pass it back to keep pagination stable while new requests arrive. Omit on the first page."

addedInput schema / properties / page / description
```
Added value: +"1-based page number to fetch."
```
addedInput schema / properties / pageSize / description
```
Added value: +"Items per page (1-100)."
```

addedInput schema / properties / scope / description

Added value: +"'me' = your own requests; 'org' = the whole organization (admins only)."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "asOf": {
+      "description": "The snapshot anchor this page was computed at — pass it back on later pages to keep the window stable while new requests arrive.",
+      "type": "string"
+    },
+    "items": {
+      "description": "The requested page of elicitations, newest first.",
+      "items": {
+        "additionalProperties": {},
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "page": {
+      "description": "The 1-based page that was served.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "pageSize": {
+      "description": "Items per page that was applied.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "scope": {
+      "description": "The scope that was served.",
+      "enum": [
+        "me",
+        "org"
+      ],
+      "type": "string"
+    },
+    "total": {
+      "description": "Total matching requests — the last page is ceil(total / pageSize).",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "items",
+    "page",
+    "pageSize",
+    "asOf",
+    "total",
+    "scope"
+  ],
+  "type": "object"
+}

First observedSep 4, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the description's added value is the pagination behavior and permission constraint: org scope is admin-only, and passing back `asOf` keeps the window stable as new requests arrive. That goes beyond what annotations declare.

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?

Three sentences, front-loaded with purpose, ordering, and pagination before the return shape and the page-computation tip. Dense but every sentence carries information; no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers pagination semantics, stability across pages, permission gating for org scope, and the returned fields — more than an output schema would require. Nothing material for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description adds real meaning by tying `asOf` to cross-page stability and showing how `total` yields the last page via ceil(total/pageSize). It largely mirrors the schema text for `scope`, but the pagination recipe is genuinely additive.

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?

States a specific verb+resource ('List your past elicitations') with scope and ordering ('newest first'), which cleanly separates it from the sibling action tools (elicit_approval, elicit_await, etc.). An agent can identify this as the read/history tool without opening the schema.

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?

Explains the `scope` choice ('me' = your own; 'org' = whole organization, admins only) and when to reuse `asOf` across pages. It gives clear context but does not explicitly name an alternative tool or state when-not-to-use this one.

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

All Elicitly Pro tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?