Skip to main content
Glama
Sign In

Koskamo

by com.koskamo
OverviewDiscussionsAdmin

List public datasets

koskamo_list_datasets
Read-onlyIdempotent

List a page of public Koskamo datasets with continuation metadata.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows in this page
offsetNoContinue from pagination.nextOffset while keeping the same filters

Output Schema

NameRequiredDescriptionDefault
datasetsYes
paginationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 50,
+  "description": "Maximum rows in this page",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Continue from pagination.nextOffset while keeping the same filters",
+  "maximum": 9007199254740891,
+  "minimum": 0,
+  "type": "integer"
+}
    • changedOutput schema / properties / datasets / items / properties / license / description
      Previous value: -"Reuse information, when supplied; consult the original source"New value: +"Reuse information from the original source, when supplied"
    • addedOutput schema / properties / pagination
      Added value: +{
+  "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"
+}
    • changedOutput schema / required
      Previous value: -[
-  "datasets"
-]New value: +[
+  "datasets",
+  "pagination"
+]
  2. Changed1 schema field changed
    • changedOutput schema / properties / datasets / items / properties / managedBy / enum
      Previous value: -[
-  "mcp-directory"
-]New value: +[
+  "mcp-directory",
+  "use-cases"
+]
  3. Changed1 schema field changed
    • addedOutput schema / properties / datasets / items / properties / managedBy
      Added value: +{
+  "description": "Documents mirror another Koskamo system of record and change only there; API revisions are refused",
+  "enum": [
+    "mcp-directory"
+  ],
+  "type": "string"
+}
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond annotations by indicating the datasets are public and that pagination continuation metadata is part of the operation.

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?

The description is a single, front-loaded sentence with no redundant or filler content. Every phrase contributes to the stated purpose, scope, or pagination behavior.

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?

The tool has rich annotations, a complete input schema, and an output schema, so the description need not explain return values or safety. It adequately states the public scope and pagination nature, though it could mention ordering or relationship to sibling retrieval tools for fuller context.

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%, with both parameters fully documented in the input schema. The description does not add detailed semantics beyond the schema, but its mention of 'page' and 'continuation metadata' aligns with limit and offset, so the baseline score of 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?

The description uses a specific verb and resource: 'List a page of public Koskamo datasets.' It clearly describes scope ('public') and pagination ('page', 'continuation metadata'). It does not explicitly distinguish this tool from siblings such as koskamo_retrieve, 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?

The description implies that this tool is used to browse paginated public datasets, but it does not state when to use it instead of alternatives like koskamo_retrieve or koskamo_get_history. No explicit exclusions or prerequisites are provided, so usage is only implied.

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

All Koskamo toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources