ts-mcp-server

Overview Schema Source Related Servers Discussions Admin

Completion Info

completionInfo

Read-only

Get autocomplete suggestions for a specific code location, showing available symbols, methods, and properties with their details.

Instructions

Get autocomplete suggestions at a position. Returns all possible completions with their kinds, sort text, and insert text. Useful for understanding what symbols, methods, or properties are available at a specific location in code.

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": {
      "file": "<file>",
      "line": "<line>",
      "offset": "<offset>"
    },
    "name": "completionInfo"
  }
}

Input Schema

Name	Required	Description
`file`	Yes	File path (absolute or relative to cwd)
`line`	Yes	1-based line number
`offset`	Yes	1-based column offset
`prefix`	No	Optional prefix to filter completions
`triggerCharacter`	No	Character that triggered completion (e.g., '.', '"', "'", '`', '/', '@', '<', '#', ' ')

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1Jul 12, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so the description's claim of returning completions adds limited behavioral context. It does not mention error handling, performance, or scope of input, making it adequate but not outstanding.

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?

Two sentences with no extraneous words. The first sentence front-loads the core action and resource, and the second adds useful detail about return values.

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 5 parameters, no output schema, and many siblings, the description adequately explains the return content and purpose. However, it could mention the output structure (array of completions) or edge cases like no completions.

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?

Schema description coverage is 100%, so the description adds no additional meaning to the parameters. It restates the overall purpose without enriching any parameter details.

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 the verb 'Get' and the resource 'autocomplete suggestions at a position', and lists the returned fields (kinds, sort text, insert text). This precisely distinguishes it from sibling tools like completionEntryDetails.

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?

It explains the tool is useful for understanding available symbols at a location, but does not explicitly mention when not to use it or name alternatives (e.g., completionEntryDetails). This leaves some ambiguity for the agent.

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