Skip to main content
Glama
delega-dev

delega-mcp

by delega-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_context_history

Read paginated context provenance history for a task to inspect past values. Filter by key and follow cursors for complete, bounded results.

Instructions

Read a bounded page of the append-only context provenance ledger. Prefer key to narrow history. Follow the JSON next_cursor using history_cursor for older entries; a Next text cursor instead continues a large current page with identical selectors. History remains complete and explicitly paginated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoOptional context key to filter history
limitNoHistory entries per API page (default 25)
cursorNoNext text cursor returned by a large read. Repeat identical selectors; changed content invalidates the cursor.
task_idYesThe task ID whose context history to read
max_charsNoMaximum response characters (default 6000); omitted data remains explicitly retrievable.
history_cursorNoAPI next_cursor from the complete previous JSON history page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.19.0
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Next text cursor returned by a large read. Repeat identical selectors; changed content invalidates the cursor.",
+  "maxLength": 100,
+  "type": "string"
+}
    • addedInput schema / properties / history_cursor
      Added value: +{
+  "description": "API next_cursor from the complete previous JSON history page",
+  "type": "string"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "History entries per API page (default 25)",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / max_chars
      Added value: +{
+  "description": "Maximum response characters (default 6000); omitted data remains explicitly retrievable.",
+  "maximum": 16000,
+  "minimum": 1000,
+  "type": "integer"
+}
    • removedInput schema / properties / task_id / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
    • addedInput schema / properties / task_id / type
      Added value: +[
+  "string",
+  "number"
+]
  2. Addedv1.18.2
  3. Removedv1.13.1
  4. Addedv1.9.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does reasonably well: it discloses append-only immutability, bounded paging, that history remains complete, and that omissions from max_chars remain retrievable. It does not state auth requirements or rate limits, but the core non-obvious behavioral traits are covered.

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 dense sentences, front-loaded with the resource and follow-up pagination mechanics. Every sentence earns its place, though the distinction between the two cursor types takes some parsing.

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 read-only ledger tool with no annotations and no output schema, the description is complete enough on behavior (paging, cursor types, retrieval guarantees) and the schema covers parameters. Minor gaps remain around auth and exact return shape, but nothing critical is missing.

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 schema already documents all six parameters thoroughly. The description reinforces how key and history_cursor behave but adds no semantics beyond what the schema provides. Baseline 3 is appropriate.

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?

States a specific verb (Read) and resource (bounded page of the append-only context provenance ledger). It is fairly clear but does not name its closest siblings (get_task_context, update_task_context) to distinguish provenance history from current context, which would have made the boundary explicit.

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?

Implies usage through guidance on key for narrowing and cursor mechanics, but never states when to use this versus get_task_context/update_task_context or any other alternative. The usage hints that exist are about pagination, not tool selection.

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