patchwork-os

getSemanticTokens

Read-only

Retrieves semantic token types and modifiers for a code file from the language server, with optional line range and token limit.

Instructions

Semantic token types and modifiers for a file from the language server.

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": {
      "filePath": "<filePath>"
    },
    "name": "getSemanticTokens"
  }
}

Input Schema

Name	Required	Description
`endLine`	No	Last line to include (1-based, inclusive, optional)
`filePath`	Yes	Workspace or absolute path
`maxTokens`	No	Max tokens to return (default: 2000, max: 5000)
`startLine`	No	First line to include (1-based, optional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 20, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already provide readOnlyHint: true, so the agent knows it's a read operation. The description adds that the data comes from 'the language server', which is additional context. However, it does not disclose any potential delays or prerequisites (e.g., file must be open).

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 13 words, front-loaded with the purpose. It contains no redundant information and is highly concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description does not explain the return format or structure of semantic tokens. It also lacks information about error cases or required file state (e.g., file must be saved/open). Given the tool's simplicity, this is incomplete.

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?

The input schema has 100% description coverage, so all parameters are explained in the schema. The description adds no additional parameter semantics beyond what the schema provides, meeting the baseline for high schema coverage.

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 clearly states it returns semantic token types and modifiers for a file from the language server. It uses a specific verb ('get') and resource ('semantic tokens for a file'), distinguishing it from sibling tools like getHover or getDocumentSymbols.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies it is for obtaining semantic token information, but does not mention when not to use it or suggest other tools like getHover or getDocumentSymbols for different needs.

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

Deploy Server