Skip to main content
Glama

reference_labels

Read-only

Resolves label IDs such as @File:LabelId or legacy @SYS12345 to text in a specified language using Visual Studio label files; returns null when the label file or ID is unavailable.

Instructions

Resolve label ids (@File:LabelId, or legacy @SYS12345) to their text in one language, from the label files Visual Studio knows. text is null when the label file or label is not found (Microsoft label files shipped only as binaries are not readable).

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": {
      "ids": "<ids>"
    },
    "name": "reference_labels"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
languageNoen-US

Output Schema

NameRequiredDescriptionDefault
okYes
errorNo
labelsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond readOnlyHint/openWorldHint the description discloses two non-obvious behaviors: text comes back null when the label file or label cannot be found, and Microsoft-supplied files shipped only as binaries are unreadable. That null-on-miss contract is the kind of detail an agent needs to avoid misreading an empty result as an error. It stops short of describing output shape or failure modes for malformed ids.

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, front-loaded with the action and resource, followed by the null-result contract. The parenthetical about binary-only label files earns its place by pre-empting a confusing miss. No filler to trim.

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?

With an output schema present the description need not spell out return values, and it still volunteers the null case. Anchoring the tool to 'the label files Visual Studio knows' also tells the agent results are workspace-bound. Minor omissions remain: default language and the batch size ceiling.

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 0%, so the description must carry the parameters, and it only partly does: it illustrates the id syntax and says results come back in 'one language'. It never mentions that language is optional with an en-US default, nor that ids are capped at 500 per call, leaving real gaps the pattern and default in the schema only partially backfill.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb ('Resolve') and resource ('label ids'), and gives concrete id forms (@File:LabelId and legacy @SYS12345) plus the source of truth (label files Visual Studio knows). It does not differentiate itself from the similarly-named sibling reference_resolve, so an agent comparing the two gets no help choosing.

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?

Usage is implied by the verb-resource pair: reach for this when you have label ids and need their text in a given language. There is no explicit statement of when not to use it, no prerequisite (e.g. whether the solution must be loaded), and no named alternative.

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