koskamo_get_historyGet the document version timeline for a public dataset: every document (including deleted ones) with the version history produced by approved revisions.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum rows in this page | |
| offset | No | Continue from pagination.nextOffset while keeping the same filters | |
| dataset | Yes | Dataset id or slug |
| Name | Required | Description | Default |
|---|---|---|---|
| dataset | Yes | ||
| history | Yes | ||
| pagination | Yes |
Changes observed during successful MCP inspections.
Input schema / additionalPropertiesAdded value: +falseInput schema / properties / limitAdded value: +{
+ "default": 50,
+ "description": "Maximum rows in this page",
+ "maximum": 100,
+ "minimum": 1,
+ "type": "integer"
+}Input schema / properties / offsetAdded value: +{
+ "default": 0,
+ "description": "Continue from pagination.nextOffset while keeping the same filters",
+ "maximum": 9007199254740891,
+ "minimum": 0,
+ "type": "integer"
+}Output schema / propertiesAdded value: +{
+ "dataset": {
+ "properties": {
+ "createdAt": {
+ "format": "date-time",
+ "type": "string"
+ },
+ "description": {
+ "type": "string"
+ },
+ "documentCount": {
+ "type": "integer"
+ },
+ "id": {
+ "format": "uuid",
+ "type": "string"
+ },
+ "license": {
+ "description": "Reuse information from the original source, when supplied",
+ "type": "string"
+ },
+ "managedBy": {
+ "description": "Documents mirror another Koskamo system of record and change only there; API revisions are refused",
+ "enum": [
+ "mcp-directory",
+ "use-cases"
+ ],
+ "type": "string"
+ },
+ "name": {
+ "type": "string"
+ },
+ "publisher": {
+ "description": "Publisher attribution, when supplied",
+ "type": "string"
+ },
+ "readOnly": {
+ "description": "Application-maintained reference datasets do not accept API revisions",
+ "type": "boolean"
+ },
+ "reviewedAt": {
+ "description": "Editorial review date, when supplied",
+ "format": "date-time",
+ "type": "string"
+ },
+ "slug": {
+ "type": "string"
+ },
+ "version": {
+ "description": "Increments every time a document write goes live",
+ "type": "integer"
+ },
+ "visibility": {
+ "enum": [
+ "public",
+ "private"
+ ],
+ "type": "string"
+ }
+ },
+ "required": [
+ "id",
+ "slug",
+ "name",
+ "description",
+ "visibility",
+ "version",
+ "documentCount",
+ "createdAt"
+ ],
+ "type": "object"
+ },
+ "history": {
+ "items": {
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "pagination": {
+ "properties": {
+ "hasMore": {
+ "type": "boolean"
+ },
+ "limit": {
+ "maximum": 100,
+ "minimum": 1,
+ "type": "integer"
+ },
+ "nextOffset": {
+ "minimum": 0,
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "offset": {
+ "minimum": 0,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "limit",
+ "offset",
+ "hasMore",
+ "nextOffset"
+ ],
+ "type": "object"
+ }
+}Output schema / requiredAdded value: +[
+ "dataset",
+ "history",
+ "pagination"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description still adds real behavioral context beyond them: results include deleted documents, and history only reflects approved revisions, which materially shapes how an agent should interpret the output. It does not discuss pagination behavior, though the schema covers that.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with a colon that enumerates scope details, no filler or repetition. Every clause (public dataset, deleted documents, approved revisions) carries information an agent needs.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists and annotations cover the safety profile, so the description's burden is mainly scope, which it discharges well. The one small gap is that it does not hint at pagination across the timeline, though the offset parameter's own description addresses continuation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so dataset, limit, and offset are already documented with defaults and bounds. The description only reinforces that the target must be a public dataset, adding marginal meaning beyond the schema, which fits the baseline of 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Get the document version timeline for a public dataset') and scopes it to every document including deleted ones. That scope implicitly separates it from siblings like koskamo_get_document and koskamo_list_revisions, but it never names them, so an agent must infer the boundary.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied by the scope phrase ('for a public dataset'), so an agent can guess this is the dataset-wide history view. However, there is no explicit when-to-use versus koskamo_get_document, koskamo_list_revisions, or koskamo_list_documents, and no stated prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.