{"version":"2.1.224","anchor":"second-lsp-tool-schema-one-strict-shape-per-operation","canonical_anchor":"second-lsp-tool-schema-one-strict-shape-per-operation","heading":"Second LSP tool schema, one strict shape per operation","tier":"internal","area":"LSP Tools","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/second-lsp-tool-schema-one-strict-shape-per-operation","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Second LSP tool schema, one strict shape per operation\n\nThe language-server tool gained a per-operation schema, but nothing chooses it over the old one.\n\n**What**\n\nA new schema for the language-server tool splits it into a separate strict object per operation (goToDefinition, findReferences, hover, documentSymbol, workspaceSymbol, goToImplementation, prepareCallHierarchy, incomingCalls, outgoingCalls), each with its own field descriptions, so arguments are validated per operation instead of against one flat shape. The old flat schema is still in the build and nothing in this group decides which one the tool presents.\n\n**Details**\n\n- The workspaceSymbol variant drops the \"(workspaceSymbol only)\" qualifier from its `query` description, since the field now exists only there.\n\n**Evidence**\n\n`The symbol name or partial name to search for. Most language servers return no results for an empty query.`\n\n- Area: LSP Tools\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}