Skip to main content
Glama

omniseek_field_skeleton

Read-only

Map a research field’s citation neighborhood from a topic or seed papers, distinguishing foundational core from date-based frontier so you can cluster related work.

Instructions

Map a research field's shape: use WHEN you need its citation neighborhood (foundational core by citations vs frontier by date) to cluster yourself, from a topic or seed papers.

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

Args: query: topic words; the top-relevance papers become the seeds. seeds: OpenAlex work ids you chose as anchors (preferred once you know the field). n_seeds: how many seeds to take from query. citers_per_seed: citing papers fetched per seed. source: "openalex" (default) or "s2" (Semantic Scholar: better arXiv coverage; nodes add influential, intent, contexts). max_nodes: node cap. fresh: bypass the cache. deadline_s: wall-clock cap (default about 25 s).

Returns {seeds, n_nodes, n_edges, edges: [[citer_id, cited_id]], nodes: [{id, title, year, date, cited_by, in_degree, concept, first_author, doi, url, is_seed, seed_ref_freq, seed_cite_freq}], _meta: {seed_titles, seed_note, degraded, deadline_hit, partial}}. in_degree = citations from inside the field; seed_ref_freq / seed_cite_freq on a non-seed node flag what your seeds miss. _meta.deadline_hit true = a partial map: retry or raise deadline_s. More: omniseek docs/TOOLS.md, omniseek_field_skeleton.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "omniseek_field_skeleton"
  }
}

Input Schema

NameRequiredDescriptionDefault
freshNo
queryNo
seedsNo
sourceNoopenalex
n_seedsNo
max_nodesNo
deadline_sNo
citers_per_seedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond readOnlyHint=true it discloses caching with a fresh bypass, a wall-clock cap (deadline_s, default ~25s), and that hitting it yields a partial map flagged in _meta.deadline_hit with a retry recommendation. It also documents source-dependent behavior (s2 adds influential/intent/contexts and better arXiv coverage) and the degraded/partial flags, which is exactly the context annotations cannot carry.

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?

The purpose is front-loaded in the first sentence, and the Args/Returns blocks are dense and scannable with no redundant restatement. The tool-name/prefix and "Not in your tool list? ToolSearch" lines, plus the docs pointer, are harness boilerplate rather than selection or invocation content, which trims a point.

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?

There is no output schema, and the description compensates fully: it enumerates the return object's fields, explains edge tuple orientation and that in_degree counts citations from inside the field, and interprets seed_ref_freq/seed_cite_freq and the _meta diagnostics. For an 8-parameter tool with zero schema documentation, this leaves nothing an agent needs in order to call it correctly.

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 description coverage is 0%, so this description carries the full burden, and it does document all eight parameters in the Args block with meaning beyond type: what query vs. seeds do, n_seeds/citers_per_seed/max_nodes as shape controls, fresh as cache bypass, and deadline_s as a time budget. The only weakness is that source is described without stating the accepted literal values explicitly ("openalex" is named; "s2" is named as shorthand, not the exact string).

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 opening sentence gives a specific verb and resource ("Map a research field's shape") and scopes it to producing a citation neighborhood split into foundational core vs. date-frontier, which is a concrete output an agent can match to a need. It does not name a sibling tool to contrast with (e.g. omniseek_graph or omniseek_search), so differentiation still relies on inference from the sibling names.

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 the triggering condition ("use WHEN you need its citation neighborhood ... to cluster yourself") and clarifies input strategy: query-derived seeds first, with "seeds ... preferred once you know the field." It gives no explicit when-not exclusions relative to the many sibling retrieval tools, so it stops short of full routing guidance.

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