Skip to main content
Glama

List Similar Authors

get_author_neighbors
Read-onlyIdempotent

Find and rank researchers whose work is closest to a given author, using an author ID or URL, to identify potential collaborators, reviewers, or related research groups.

Instructions

List researchers whose work is closest to one author's, ranked.

Use for "who else works on what X works on": finding possible collaborators, reviewers or related groups. Pass an author id or URL.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
author_id_or_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive, so the safety profile is covered. The description adds that results are ranked, which is genuine behavioral information, but it never explains the ranking basis, result size, or ordering ties.

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?

Short and front-loaded: the core action and ranking behavior appear first, then the use case. The closing sentence is a fragment but it earns its place by telling the agent what input form to pass.

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?

With an output schema and full annotations supplied, the description need not explain return values. Still, for a tool with a default limit of 8 and an offset, the absence of any pagination or result-volume guidance is a meaningful gap.

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 0%, so the description must carry the load. It does clarify that the required parameter accepts either an author id or a URL, but limit and offset are never mentioned, leaving pagination semantics entirely undisclosed.

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: list researchers closest to a given author, returned ranked. That distinguishes it from siblings like get_author_papers or get_author_directions, though no sibling is named explicitly.

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 a concrete use case in the form of a question ("who else works on what X works on") plus the downstream goals: collaborators, reviewers, related groups. No explicit when-not or named alternative, so it stops short of a 5.

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