Skip to main content
Glama

Resolve Edge

resolve_edge
Read-only

Resolve an edge tag to the current EdgeN index; returns an error if the tag is missing or ambiguous.

Instructions

Resolve an edge tag to the current EdgeN index. Errors on miss or ambiguity.

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": {
      "handle": "<handle>",
      "tag": "<tag>"
    },
    "name": "resolve_edge"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagYes
handleYes
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral detail that the call fails on miss or ambiguity, but it does not explain error shape, return format, or any constraints on the required handle.

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 short sentences, front-loaded with the core action and followed by failure behavior. There is no redundant or wasted language.

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?

The description is adequate for a read-only resolver and notes error behavior, but without an output schema it should clarify what the resolved EdgeN index is returned as. It also leaves the required handle parameter unexplained, which is a meaningful gap for a three-parameter tool.

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

Parameters2/5

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

Schema description coverage is only 33%, with workspace documented but tag and handle undocumented. The description mentions 'edge tag' but does not define what a tag is, what handle refers to, or how workspace affects resolution, so it does not compensate for the missing schema descriptions.

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?

The description gives a specific verb and resource: 'Resolve an edge tag to the current EdgeN index.' It clearly states the transformation performed, but it does not distinguish this from nearby tools such as resolve_face, list_edges, or register_handle.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It says the tool errors on miss or ambiguity, which implies a strict lookup, but it gives no guidance on when to use resolve_edge versus list_edges, resolve_face, or other edge-related tools. There are no explicit prerequisites or alternative-selection rules.

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