Soleil Clusters

Find by identifier

resolve_identifier

Read-onlyIdempotent

Finds the board or card carrying an identifier another system assigned (a ShotGrid or ftrack id, a checksum, an import's source_url). Prefer it to searching by name when you have a real id.

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": {
      "scope": "<scope>",
      "value": "<value>"
    },
    "name": "resolve_identifier"
  }
}

Input Schema

Name	Required	Description
`type`	No	Only this kind
`scope`	Yes	The system that assigned it, e.g. "shotgrid"
`value`	Yes	Its identifier there, e.g. "Shot:12345"
`workspace_id`	No	Only this workspace

Output Schema

Name	Required	Description	Default
`scope`	No
`value`	No
`matches`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds useful context about what kinds of identifiers exist and that resolution spans boards or cards, though it does not say what happens when nothing matches or when multiple records match.

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 core action and followed by the routing advice. No filler or restatement of the title.

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?

An output schema exists, so return values need not be explained, and the tool is simple with fully documented parameters. The only gap is not-found or ambiguous-match behavior, which an agent would want to know before calling.

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?

Schema coverage is 100%, so the baseline is 3, but the description enriches the 'scope' parameter by enumerating real identifier systems (ShotGrid, ftrack, checksum, source_url) beyond the schema's single 'shotgrid' example. It does not clarify the optional type or workspace_id filters, which the schema already handles.

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?

States a specific verb and resource ('Finds the board or card') plus the distinguishing concept: an identifier assigned by another system, with concrete examples (ShotGrid, ftrack, checksum, source_url). This clearly separates it from name-based lookup siblings like search.

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

Usage Guidelines5/5

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

Explicitly says to prefer this over searching by name when a real external id is available, naming the alternative approach and the condition that selects it. That is exactly the when-to-use routing an agent needs.

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

All Soleil Clusters tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.