Skip to main content
Glama

Get Author

get_author_context
Read-onlyIdempotent

Retrieve a researcher's profile with their main papers and shaped research directions to answer who they are in research terms or what they are known for.

Instructions

Profile one researcher: their main papers and the directions they shaped.

Use for "who is X in research terms" or "what is X known for".

Author profiles describe research output (papers, directions, impact). A free-text affiliation field may be present but can be incomplete or outdated and may not represent current employment; the corpus has no biography or employment history, so do not infer those from this data.

view selects the response shape:

  • "context" (default, recommended): Lacuna's compact author context — capped readable papers and an impact_directions list (named research directions) in place of the raw numeric impact_clusters telemetry, with the duplicated nested author record dropped server-side.

  • "full": the bounded full-shape author context (raw impact_clusters, nested author record; server collections are capped at 100).

Set include_neighbors=True to include similar authors as named, linkable records. Neighbor computation may add significant server latency.

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_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNocontext
author_id_or_urlYes
include_neighborsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description still adds real value: the affiliation field may be stale and does not imply current employment, the corpus lacks biography/employment data, neighbor computation adds server latency, and server collections cap at 100. That extra context is meaningful, though a 3 reflects that much of this is data caveats rather than operational 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?

Purpose and usage are front-loaded in two short sentences, then the view enum is expanded as a tight bulleted list, followed by the neighbor flag. The affiliation disclaimer is the longest passage but earns its place as a data-integrity warning.

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?

An output schema exists, so return values need not be restated, and the description correctly focuses on view selection, the neighbor tradeoff, and corpus limitations. An agent has everything needed to choose parameters and interpret results with appropriate caution.

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 the description carries the burden and largely succeeds: it documents what each view value returns (context's capped papers plus impact_directions vs full's raw impact_clusters and nested author record) and explains include_neighbors' effect and latency cost. Only author_id_or_url's expected format is left implicit from its name.

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 concrete verb and resource: profiling one researcher via their main papers and the research directions they shaped, plus the framing question "who is X in research terms." It does not explicitly contrast itself with siblings such as get_author_papers, get_author_directions, or get_author_neighbors, so an agent must infer the boundary from the tool names alone.

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 explicit usage contexts ("who is X in research terms", "what is X known for") and recommends view="context" as the default, which is actionable guidance. It stops short of stating when to prefer a sibling tool or when this tool is insufficient (e.g. for exhaustive paper lists).

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