Skip to main content
Glama

List Institution Authors

get_institution_authors
Read-onlyIdempotent

Fetch a page of authors affiliated with a Lacuna institution, ordered by paper count, and page through the full list using offset and limit.

Instructions

Fetch one page of authors who list a Lacuna institution on their papers.

Each author appears because published papers list this institution as one of their affiliations. This is a record of research output, not a staff directory: it may be incomplete or out of date and does not show current employment. Each entry has the author's name, Lacuna page and paper count; there are no contact details or other personal data.

Results are ordered by paper count. Use authors_total, authors_returned, authors_offset, and authors_truncated to page through the complete list.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
institution_key_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
Behavior4/5

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

Annotations already cover read-only, idempotent and non-destructive semantics, so the description wisely spends its words elsewhere: ordering by paper count, the incompleteness/staleness caveat, the absence of contact data, and the exact response fields used for paging. It stops short of describing auth or rate-limit behavior, which keeps it from a 5.

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 scope statement is front-loaded and each sentence adds distinct information (semantics, caveats, ordering, pagination). It is slightly longer than strictly needed, since the field inventory overlaps with the output schema.

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?

For a three-parameter read tool with an output schema, the definition covers the important ambiguities: what the records mean, their ordering, and how to page. The remaining gap is identifier format for the required institution parameter, which is the one thing that would block a correct call.

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%, so the description has to carry all three parameters and only partially does: it explains paging conceptually and points at authors_offset/authors_truncated, but never states what `limit` defaults to or caps at, nor whether `institution_key_or_url` accepts a bare key, a full URL, or both.

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 ('Fetch one page of authors who list a Lacuna institution') plus the scope ('on their papers'). It cleanly separates this from the author-side siblings like get_author_papers, but never names an alternative tool such as get_institution_context, so the differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied through the framing ('record of research output, not a staff directory'), which tells the agent when this data is and isn't appropriate. However, there is no explicit when-to-use/when-not-versus-siblings guidance and no stated prerequisite for obtaining an institution key or URL.

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