ChatGPT2LocalBridge

by Harzva

Overview Schema Source Related Servers Discussions Admin

Local

Resolve Workspace

workspace.resolve

Read-only

Resolves a workspace name to its local project path, or returns the default workspace path if no name is provided.

Instructions

Resolve a workspace name to its project path. If name is omitted, resolves the default workspace.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "workspace.resolve"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No

Output Schema

Name	Required	Description	Default
`name`	Yes
`path`	Yes
`createdAt`	Yes
`updatedAt`	Yes
`isDefault`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 19, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The description adds the default behavior beyond the readOnlyHint annotation, and there is no contradiction. It clarifies that the tool is non-destructive and returns a path.

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 concise sentences with no fluff. The key information is front-loaded, and every sentence is informative.

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

Completeness5/5

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

For a simple tool with one optional parameter and an output schema, the description covers the main purpose and default case sufficiently.

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 description adds meaning to the single 'name' parameter by indicating it is optional and explaining the behavior when omitted, but does not specify expected format or constraints.

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 'Resolve' and the resource 'workspace name to its project path', which is specific and distinguishes from sibling tools like workspace.add or workspace.list.

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?

The description provides context for when name is omitted (default workspace) but does not explicitly state when to use this tool over alternatives or when not to use it.

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