Skip to main content
Glama

omniseek_resolve_identity

Read-only

Resolve a person's name to ranked candidate author IDs for disambiguation; add institution, field, or paper hints to narrow common names.

Instructions

Resolve a PERSON's name to candidate author ids: the shared front door for EVERY relationship tool. It never picks: it returns ranked candidates for you to disambiguate.

Tool name: omniseek_resolve_identity (your MCP config adds its own prefix; never guess one). Not in your tool list? ToolSearch "omniseek_resolve_identity".

Args: name: the person's name. hint: an institution or field; only re-orders candidates. source: "auto" (OpenAlex, plus Semantic Scholar when the top hit is sparse), "openalex" or "s2". paper: arXiv id / DOI / title of a known paper by this person; pins a common-name junior.

Returns {query, source, candidates: [{id, source, name, works_count, cited_by, institution, via_paper?}], ambiguous, note, likely_same_person?: [{source, ids, name, merge_token, note}], degraded?}. ambiguous true = confirm with a hint, a paper or a known coauthor. merge_token ("A1+A2") goes straight into omniseek_coauthors. degraded = the OpenAlex lookup failed, so an empty result is missing data: retry, or pass source="s2" or paper=. More: omniseek docs/TOOLS.md, omniseek_resolve_identity.

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

Input Schema

NameRequiredDescriptionDefault
hintNo
nameYes
paperNo
sourceNoauto

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries most of the load and does so well: ranked-not-chosen output, ambiguity semantics, degraded-lookup meaning (empty result = missing data, not no match), and a merge_token that feeds omniseek_coauthors. Minor gap: no indication of latency, rate limits, or candidate list size.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Args and Returns are cleanly block-structured and front-loaded with the purpose. Some space is spent on meta-boilerplate about MCP prefixes and ToolSearch fallback plus a docs pointer, which is useful for invocation but not about the tool's semantics.

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?

Despite no output schema, the return shape is fully enumerated field-by-field, including optional fields and the degraded flag's meaning. For a four-parameter read tool with a single annotation, an agent has everything needed to call it and interpret the response.

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

Parameters5/5

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

Schema coverage is 0% (bare titles and defaults only), and the description compensates fully: hint is 'only re-orders candidates' (a crucial non-filtering semantic), source enumerates its three values with what 'auto' actually does, and paper is explained as pinning a common-name junior author.

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 ('Resolve a PERSON's name to candidate author ids') and immediately positions itself as 'the shared front door for EVERY relationship tool', which distinguishes it from all sibling lookup/graph tools. The 'it never picks' clause clarifies the output contract in the same breath.

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?

Explicit when-to-use (entry point for relationship tools), explicit behavioral boundary (never disambiguates for you), and explicit remedies for ambiguity: confirm with a hint, a paper, or a known coauthor. Degraded-state guidance ('retry, or pass source="s2" or paper=') names concrete alternatives rather than leaving the agent to guess.

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