Skip to main content
Glama
Sign In

Schemastore

by io.github.pipeworx-io
OverviewDiscussionsAdmin

List Schemas

list_schemas
Read-onlyIdempotent

List SchemaStore catalog entries. Optional case-insensitive filter on name/description/fileMatch.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 10,
      "filter": "github"
    },
    "name": "list_schemas"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1-500 (default 50)
filterNoe.g. "github", "tsconfig", "openapi"

Output Schema

NameRequiredDescriptionDefault
totalYesTotal number of schemas in catalog
matchesYesNumber of schemas matching the filter
resultsYesFiltered catalog entries (up to limit)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "filter": "github",
+    "limit": 10
+  },
+  {
+    "filter": "openapi"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "matches": {
+      "description": "Number of schemas matching the filter",
+      "type": "number"
+    },
+    "results": {
+      "description": "Filtered catalog entries (up to limit)",
+      "items": {
+        "properties": {
+          "description": {
+            "description": "Schema description",
+            "type": "string"
+          },
+          "fileMatch": {
+            "description": "Glob patterns matching filenames",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "name": {
+            "description": "Schema name",
+            "type": "string"
+          },
+          "url": {
+            "description": "Schema URL",
+            "type": "string"
+          },
+          "versions": {
+            "additionalProperties": {
+              "type": "string"
+            },
+            "description": "Schema versions mapping",
+            "type": "object"
+          }
+        },
+        "required": [
+          "name",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Total number of schemas in catalog",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "matches",
+    "results"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already indicate the tool is read-only, non-destructive, idempotent, and open-ended. The description adds that filtering is case-insensitive and applies to name, description, and fileMatch. This provides additional behavioral context beyond the annotations.

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 sentence of 16 words, efficiently conveying the essential behavior. It is front-loaded with the main action and includes the key detail about filtering. No unnecessary verbiage.

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?

Given the presence of an output schema and comprehensive annotations, the description adequately covers the tool's functionality. It explains the filtering capability but does not mention pagination or limit behavior beyond what is in the schema.

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?

The input schema describes both parameters with basic examples. The description clarifies that the filter is case-insensitive and applies to specific fields (name, description, fileMatch), which adds meaning beyond the schema's simple examples.

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 clearly states the tool lists SchemaStore catalog entries and mentions the optional filter. The purpose is specific, but it does not explicitly differentiate from sibling tools like 'fetch_schema' or 'find_schema_for', which are also schema-related.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. For example, if a user needs a specific schema, they might prefer 'fetch_schema' or 'find_schema_for' instead. The description only mentions the filter capability without explaining when it is appropriate.

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

All Schemastore toolsInspect
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