Skip to main content
Glama

LintSchema

Read-onlyIdempotent

Lint a GraphQL schema document against the graph's lint rules and return each diagnostic's coordinate, severity level, message, rule, and source location, plus the error, warning, total, and ignored counts. This is the same check that rover graph lint and rover subgraph lint run. Nothing is published and no state changes. Provide the graph ID and the schema as SDL. The rules that run are the ones enabled in the graph's linter configuration, so a missing diagnostic can mean the rule is turned off. Optionally provide baseSdl to report only the diagnostics that the new schema introduces against that base; empty diagnostics then mean the new schema introduces no violations of the enabled rules, and ignored diagnostics are counted in ignoredCount, not listed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "graphId": "<graphId>",
      "sdl": "<sdl>"
    },
    "name": "LintSchema"
  }
}

Input Schema

NameRequiredDescriptionDefault
sdlYesThe schema to lint.
baseSdlNoThe schema to diff rule violations against, if not provided the full set of rule violations will be returned for the proposed sdl.
graphIdYes

Output Schema

NameRequiredDescriptionDefault
dataNo
errorsNo
extensionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the 'nothing is published and no state changes' line is consistent but partly redundant. The description adds valuable context beyond annotations: rules come from the graph's linter configuration, missing diagnostics can mean a rule is disabled, and `baseSdl` changes the reported set while moving ignored diagnostics to `ignoredCount`. It does not cover auth or rate limits, but for a lint operation it discloses the key behavioral nuances.

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?

The description is front-loaded with the core action and uses short sentences that mostly earn their place. It spends some words restating return fields and `baseSdl` semantics already present in the schema/output schema, so it is not maximally tight, but it is well organized and not verbose.

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 read-only annotations and existing output schema, the description supplies the missing behavioral context an agent needs: side-effect profile, rule-configuration caveat, and `baseSdl` diff semantics. The main residual gaps are the absence of explicit routing guidance versus related lint/result/check tools and the missing `graphId` format, but for calling this tool correctly the definition is essentially complete.

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?

Schema coverage is 67%; `sdl` and `baseSdl` have schema descriptions, while `graphId` has none. The description adds that `graphId` identifies the graph, that `sdl` must be SDL, and most importantly explains `baseSdl`'s diff behavior and what empty/ignored results mean. This meaningfully supplements the schema, though it still does not specify the expected `graphId` format.

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 first sentence states a specific verb and resource: linting a GraphQL schema document against graph lint rules and returning diagnostics with counts. The reference to `rover graph lint`/`rover subgraph lint` and the explicit 'nothing is published' line distinguish this from publishing or state-changing schema operations. The tool's purpose is clear without opening the schema.

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 explains required inputs ('Provide the graph ID and the schema as SDL') and the optional `baseSdl` diff use case, including what empty and ignored diagnostics mean. However, it does not explicitly say when to choose this over sibling tools such as `GetLintResults`, `GetSchemaChecks`, or `RunSchemaCheck`, and it gives no when-not-to-use guidance. Usage is therefore clear for the tool itself but not comparative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources