Skip to main content
Glama

Resolve an entity

resolve_entity
Read-onlyIdempotent

Resolve a label or typed ID to cited candidates. Returns ambiguity instead of merging names. Use a returned id with get_entity_graph or get_* tools.

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": {
      "query": "<query>"
    },
    "name": "resolve_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
limitNo
queryYes
offsetNo

Output Schema

NameRequiredDescriptionDefault
hintNo
countYes
offsetYes
resultsYes
has_moreYes
ambiguousYes
next_offsetNo
snapshot_idYes
suggestionsNo
total_matchesYes
effective_limitNo
requested_limitNo
response_limitedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "person",
      -  "project",
      -  "section",
      -  "organisation",
      -  "location",
      -  "subject",
      -  "format",
      -  "language",
      -  "collection",
      -  "research_item",
      -  "publication",
      -  "journal",
      -  "podcast",
      -  "video",
      -  "playlist"
      -]New value: +[
      +  "person",
      +  "project",
      +  "section",
      +  "organisation",
      +  "location",
      +  "subject",
      +  "format",
      +  "language",
      +  "collection",
      +  "research_item",
      +  "publication",
      +  "journal",
      +  "podcast",
      +  "video",
      +  "chronicle",
      +  "playlist"
      +]
    • changedOutput schema / properties / results / items / properties / type / enum
      Previous value: -[
      -  "person",
      -  "project",
      -  "section",
      -  "organisation",
      -  "location",
      -  "subject",
      -  "format",
      -  "language",
      -  "collection",
      -  "research_item",
      -  "publication",
      -  "journal",
      -  "podcast",
      -  "video",
      -  "playlist"
      -]New value: +[
      +  "person",
      +  "project",
      +  "section",
      +  "organisation",
      +  "location",
      +  "subject",
      +  "format",
      +  "language",
      +  "collection",
      +  "research_item",
      +  "publication",
      +  "journal",
      +  "podcast",
      +  "video",
      +  "chronicle",
      +  "playlist"
      +]
  2. Changed5 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / additionalProperties
      Removed value: -false
    • removedOutput schema / properties / results / items / additionalProperties
      Removed value: -false
    • removedOutput schema / properties / suggestions / items / additionalProperties
      Removed value: -false
  3. Changed1 schema field changed
    • removedInput schema / properties / limit / maximum
      Removed value: -9007199254740991
  4. Changed2 schema fields changed
    • addedOutput schema / properties / hint
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / suggestions
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "amira_url": {
      +        "type": "string"
      +      },
      +      "id": {
      +        "type": "string"
      +      },
      +      "name": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "name",
      +      "amira_url"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  5. Added

TDQS

A4/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 safety is covered. The description adds a genuinely useful behavioral trait beyond them: 'Returns ambiguity instead of merging names', warning that multiple candidates may come back and that the tool will not auto-disambiguate. It omits what happens on zero matches and says nothing about limit/offset paging behavior.

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?

Three short sentences with zero filler. The core behavior is front-loaded, the disambiguation contract follows, and the downstream usage hint closes it out.

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 no explanation, and the description covers purpose, disambiguation semantics and the follow-up call. Relative to a four-parameter resolver, the main remaining gap is pagination guidance for limit/offset when many candidates are returned.

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?

Schema description coverage is 0% across four parameters, so the description must carry meaning. It partially does by mapping 'label or typed ID' onto query and type, but limit and offset are never explained, nor are bounds or the effect of the type enum on matching.

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?

States a specific verb and resource: resolve a label or typed ID into cited candidates. That is clearly distinct from the get_* retrieval siblings, which consume IDs rather than produce them. It stops short of naming a direct alternative such as 'search', so sibling differentiation is implied by the workflow rather than asserted.

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?

Gives an explicit downstream instruction: 'Use a returned id with get_entity_graph or get_* tools', which tells the agent this is a first step in a two-stage flow. It does not state when NOT to use it (e.g., when you already have an id and should skip straight to get_*), so there is no exclusion guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.