Skip to main content
Glama
Sign In
sharplens-mcp

sharplens-mcp

by pzalutski-pixel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

roslyn:go_to_definition

Navigate to a symbol's definition by providing file path and zero-based line/column coordinates. Returns the exact definition location without finding all references.

Instructions

Fast navigation to symbol definition. Returns the definition location without finding all references. IMPORTANT: Uses ZERO-BASED coordinates (editor line 10 = pass line 9).

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>",
      "line": "<line>",
      "column": "<column>"
    },
    "name": "roslyn:go_to_definition"
  }
}

Input Schema

NameRequiredDescriptionDefault
lineYesZero-based line number (editor line - 1)
columnYesZero-based column number (editor column - 1)
filePathYesAbsolute path to source file containing the symbol

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, description carries full burden. It clearly discloses zero-based coordinate system, which is critical for correct usage. However, it omits other behavioral traits like error behavior or performance expectations.

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, both purposeful: first states action and key differentiator, second explains critical coordinate aspect. No filler or redundancy.

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

Completeness3/5

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

Tool has no output schema, but description does not specify return value format (e.g., file path, line, column). While simple, the return details are needed for agent to interpret results. Incomplete for a 3-param tool with no output schema.

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 has 100% coverage with clear descriptions for all 3 parameters. Description reinforces zero-based coordinate usage but adds no additional semantics beyond what the schema already provides.

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?

Description clearly states verb ('navigate to symbol definition'), resource ('definition'), and key distinction ('without finding all references'). Differentiates from sibling by emphasizing it does not find all references, which is a sibling behavior.

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?

Description implies usage when only definition location is needed, via 'without finding all references', but no explicit when-to-use, when-not-to-use, or alternative tools mentioned. Lacks guidance on prerequisites or context.

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

Deploy Server

Other Tools