Priority — TypeScript Compiler Intelligence

Get Capabilities

get_capabilities

Read-onlyIdempotent

Return Semantic Reader capabilities, limits, billing and discovery facts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_capabilities"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`ops`	No
`name`	Yes
`input`	No
`stage`	No
`billing`	No
`queries`	No
`version`	Yes
`discovery`	No
`languages`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 16, 2026
- removedOutput schema / properties / description
```
Removed value: -{
-  "type": "string"
-}
```

Changed1 schema field changedSep 14, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "billing": {
+      "additionalProperties": {},
+      "type": "object"
+    },
+    "description": {
+      "type": "string"
+    },
+    "discovery": {
+      "additionalProperties": {},
+      "type": "object"
+    },
+    "input": {
+      "additionalProperties": {},
+      "type": "object"
+    },
+    "languages": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "name": {
+      "type": "string"
+    },
+    "ops": {
+      "additionalProperties": {},
+      "type": "object"
+    },
+    "queries": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "stage": {
+      "type": "string"
+    },
+    "version": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "version"
+  ],
+  "type": "object"
+}

First observedSep 13, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds no extra behavioral context such as authentication, rate limits, or data freshness, but for a read-only capability query this is acceptable.

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?

Single sentence, front-loaded with the verb 'Return', and every word conveys meaning. There is no redundancy or filler.

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 zero parameters, an output schema, and annotations covering safety, the description is sufficient. It names the categories of information returned, which is all an agent needs to decide to call it.

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 tool has zero parameters, so there are no parameter semantics for the description to add. The baseline of 4 applies here, and the description does not need to compensate for any schema gaps.

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 verb and resource: 'Return Semantic Reader capabilities, limits, billing and discovery facts.' This clearly distinguishes it from sibling tools that focus on code symbols (find_symbol, get_type, etc.), so an agent can easily tell this is a system-level capability query.

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 the tool is for retrieving capability and billing information, but it does not explicitly state when to use it or mention alternatives. Since it is a simple zero-parameter query, the gap is minor but still present.

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

All Priority — TypeScript Compiler Intelligence 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.

Resources

Need Help?