Schemastore

Find Schema For

find_schema_for

Read-onlyIdempotent

Match a config filename against the SchemaStore catalog (schemastore.org) to find which JSON Schemas declare a fileMatch glob covering it, for example package.json, tsconfig.json, or .github/workflows/ci.yml. Returns the matching catalog entries with schema name, description, fileMatch globs, and the json.schemastore.org schema URL. Answers which JSON Schema validates a given config file so an editor or linter can be pointed at it.

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": {
      "filename": "package.json"
    },
    "name": "find_schema_for"
  }
}

Input Schema

Name	Required	Description	Default
`filename`	Yes	e.g. package.json, .github/workflows/ci.yml

Output Schema

Name	Required	Description	Default
`matches`	Yes	Catalog entries with matching fileMatch globs
`filename`	Yes	Input filename searched

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "filename": "package.json"
+  },
+  {
+    "filename": ".github/workflows/ci.yml"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "filename": {
+      "description": "Input filename searched",
+      "type": "string"
+    },
+    "matches": {
+      "description": "Catalog entries with matching fileMatch globs",
+      "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"
+    }
+  },
+  "required": [
+    "filename",
+    "matches"
+  ],
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds the matching logic and what is returned (schema name, description, fileMatch globs, URL), which is useful 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 three sentences, each earning its place: purpose, examples, return payload, and use case. No fluff or repetition.

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?

Given the simple one-parameter tool, presence of an output schema, and comprehensive annotations, the description fully covers the tool's function, return values, and use case. No missing critical information.

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 schema fully describes the filename parameter (100% coverage), so the baseline is 3. The description reinforces with examples like package.json and .github/workflows/ci.yml, adding clarity about what constitutes a config filename.

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?

The description states a specific action: 'Match a config filename against the SchemaStore catalog...' and explains it returns matching catalog entries. It clearly distinguishes from sibling tools like fetch_schema by focusing on identifying which JSON Schema validates a given config file.

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?

The description gives clear context: use when you need to determine which JSON Schema validates a config file, with the explicit purpose of pointing an editor or linter. It does not explicitly name alternatives or state when not to use it, but the use case is well-defined.

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

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