Skip to main content
Glama

Get Institution

get_institution_context
Read-onlyIdempotent

Summarizes a university, lab or company's research output with paper and author counts plus top publishing authors, answering questions like what an institution publishes or who its most active authors are.

Instructions

Describe the research output of a university, lab or company.

Use for "what does X publish" or "who are the most active authors at X".

The context summarizes the institution's research output: its paper and author counts and the authors who publish most often under it. Affiliations come from the author affiliations listed on published papers, not from staff directories, and may be incomplete or out of date. The response has no contact details, biographies or employment records.

view selects the response shape:

  • "context" (default, recommended): compact institution context — capped top authors with the duplicated institution block dropped server-side.

  • "full": the complete institution context shape (duplicated institution record and a bounded author list with explicit truncation metadata).

Use get_institution_authors to page through the complete author 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_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNocontext
institution_key_or_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/openWorld annotations, it discloses data provenance (affiliations derived from published papers, not staff directories), known staleness/incompleteness, and explicit negative scope (no contact details, biographies or employment records). It also explains the server-side transformation behind each view, which annotations cannot convey.

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?

Front-loaded summary, then example queries, then caveats, then a structured enumeration of view modes. Every sentence adds decision-relevant information; nothing is redundant with the schema or annotations.

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?

With an output schema present, the description needn't document return values, yet it still sketches the response shape (paper/author counts, top authors, truncation metadata) and points to the paging sibling. For a two-parameter read tool, nothing an agent needs to call it correctly is missing.

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 must carry parameter meaning; it does so well for view, spelling out each enum value, the default/recommended choice, and what gets dropped or truncated. institution_key_or_url is left uncharacterized (no hint about accepted key formats vs. URLs), which is the remaining gap.

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+resource ("Describe the research output of a university, lab or company") and immediately grounds it with two example questions an agent would actually receive. It is clearly distinguishable from get_institution_authors and from author/venue siblings.

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 concrete when-to-use phrasings ("what does X publish", "who are the most active authors at X") and routes paging of the full author list to get_institution_authors. It stops short of any when-not or exclusion guidance, so it is strong but not exhaustive.

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