Geond Agent Protocol

Suggest workspace aliases

suggest_workspace_aliases

Avoid creating duplicate workspaces by checking existing workspaces that match a new alias URI using identity fingerprints.

Instructions

Purpose: Suggest existing workspaces that may match a new alias URI based on identity fingerprints. When to use: call before creating a new workspace for a repo that may have moved. Inputs: alias_uri is the new path; fingerprints are observed durable identifiers. Side effects: none beyond database reads. Output: candidate workspace matches with confidence evidence. Failure modes: returns an empty list when no fingerprints overlap.

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": {
      "alias_uri": "<alias_uri>",
      "fingerprints": "<fingerprints>"
    },
    "name": "suggest_workspace_aliases"
  }
}

Input Schema

Name	Required	Description	Default
`alias_uri`	Yes	New workspace URI or local path being evaluated.
`fingerprints`	Yes	Observed identity fingerprints for the candidate workspace.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 3, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description discloses side effects ('none beyond database reads') and failure modes ('returns an empty list when no fingerprints overlap'). This provides sufficient transparency for safe use.

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?

The description is structured with labeled sections (Purpose, When to use, Inputs, etc.) and is concise with no redundant information. Every sentence adds value.

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?

Given the tool's simplicity (2 params, no nested objects) and presence of an output schema, the description covers purpose, usage, side effects, output, and failure modes comprehensively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaning beyond the schema: 'alias_uri is the new path; fingerprints are observed durable identifiers.' This clarifies the nature of the parameters, especially 'fingerprints' as durable identifiers. Schema coverage is 100%.

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 tool's purpose: to suggest existing workspaces that may match a new alias URI based on identity fingerprints. This distinguishes it from sibling tools like 'list_workspace_aliases' and 'register_workspace_alias'.

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?

The description provides explicit guidance on when to use: 'call before creating a new workspace for a repo that may have moved.' This gives clear context, though it does not explicitly mention alternatives.

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