Skip to main content
Glama

Resolve Face

resolve_face
Read-only

Converts a face tag into its current FaceN index for tools that require explicit face references, returning an error when the tag is missing or ambiguous.

Instructions

Resolve a face tag to the current FaceN index. Errors on miss or ambiguity.

Use this when you need to pass a (object, 'FaceN') reference into a tool that doesn't accept tags directly (e.g. legacy FEM constraints).

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_face"
  }
}

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

A3.5/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavior by saying it errors on miss or ambiguity. It does not explain what constitutes ambiguity, how errors are surfaced, or the exact return format beyond 'FaceN index.'

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 definition is two short sentences with zero filler. The core purpose is front-loaded, followed immediately by the usage condition.

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?

For a simple read-only resolver with no output schema, the description explains the intended result and error behavior. However, it leaves the handle/tag input semantics under-specified, and the ambiguity behavior is only mentioned without detail.

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 handle and tag undocumented in the schema. The description implies tag means face tag and references an object, but it does not clearly define the handle parameter, accepted tag syntax, or how workspace affects resolution, so it only partially compensates for the schema gap.

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 a face tag to the current FaceN index.' That is much clearer than the name alone. It does not explicitly distinguish itself from nearby siblings such as resolve_edge or list_faces, but the face-specific scope is evident.

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?

It states a concrete usage condition: use when passing a (object, 'FaceN') reference into a tool that does not accept tags directly, with legacy FEM constraints as an example. It does not name when not to use it or list alternatives, but the intended context is clear.

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