Skip to main content
Glama
u9401066

pubmed-search-mcp

by u9401066
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

configure_institutional_access

DestructiveIdempotent

Set your institution's link resolver to access paywalled articles through library subscriptions. Configure OpenURL URLs or presets for full-text retrieval.

Instructions

Configure your institution's link resolver for full-text access.

═══════════════════════════════════════════════════════════════════════════════ 🏛️ INSTITUTIONAL ACCESS CONFIGURATION ═══════════════════════════════════════════════════════════════════════════════

This tool configures OpenURL link resolver integration, allowing you to access paywalled articles through your institution's library subscription.

Remote service callers may call this tool with no configuration arguments to inspect the operator-installed configuration, but cannot mutate the server-owned, deployment-wide OpenURL settings. Configure those at deployment time or from a trusted local server instead.

═══════════════════════════════════════════════════════════════════════════════ HOW IT WORKS: ═══════════════════════════════════════════════════════════════════════════════

  1. Your library subscribes to journals through publishers

  2. Library provides a "Link Resolver" service (SFX, 360 Link, Primo, etc.)

  3. OpenURL passes article metadata to the resolver

  4. Resolver checks your subscriptions and provides full-text access

═══════════════════════════════════════════════════════════════════════════════ USAGE: ═══════════════════════════════════════════════════════════════════════════════

Option 1: Use a preset (easiest) ───────────────────────────────── configure_institutional_access(preset="ntu")

Available presets:

  • 台灣: "ntu" (台大), "ncku" (成大), "nthu" (清大), "nycu" (陽明交大)

  • 美國: "harvard", "stanford", "mit", "yale"

  • 英國: "oxford", "cambridge"

  • 通用: "sfx", "360link", "primo" (需要 resolver_url)

Option 2: Custom URL ───────────────────── configure_institutional_access( resolver_url="https://your.library.edu/openurl" )

Option 3: Disable ───────────────────── configure_institutional_access(enable=False)

═══════════════════════════════════════════════════════════════════════════════ FINDING YOUR RESOLVER URL: ═══════════════════════════════════════════════════════════════════════════════

  1. Go to your library's website

  2. Look for "Find Full Text", "Link Resolver", or "OpenURL"

  3. Or search: "[Your University] link resolver"

  4. The URL usually looks like:

Args: resolver_url: Your institution's link resolver URL preset: Use a known institution's preset configuration enable: Whether to enable OpenURL links (default: True) Returns: Configuration status message

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enableNo
presetNo
resolver_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.7.2
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / preset / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "ntu",
+      "ncku",
+      "nthu",
+      "nycu",
+      "harvard",
+      "stanford",
+      "mit",
+      "yale",
+      "oxford",
+      "cambridge",
+      "sfx",
+      "360link",
+      "primo",
+      "test_free"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / resolver_url / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 8192,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / test
      Removed value: -{
-  "default": true,
-  "title": "Test",
-  "type": "boolean"
-}
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "configure_institutional_accessOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.5.16

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=true. The description adds meaningful behavioral context: remote callers can inspect the operator-installed configuration with no arguments, cannot mutate server-owned OpenURL settings, and should configure those via deployment or a trusted local server. It does not explicitly state what happens if a remote caller attempts mutation or whether applying a preset overwrites existing settings.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured and front-loads the core purpose and security constraint, but it is long and includes nonessential content such as the four-step 'HOW IT WORKS' explanation and detailed 'FINDING YOUR RESOLVER URL' instructions. The ASCII decoration adds visual structure but also verbosity; it is more of a user guide than a tightly focused agent tool definition.

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?

Given no output schema, the description at least states 'Returns: Configuration status message.' It covers all invocation modes, parameter semantics, preset options, and the important remote-vs-deployment permission distinction. It would be more complete if it pointed to test_institutional_access or diagnose_institutional_access for verifying or troubleshooting the configured access, and if it described the return format more precisely.

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%, but the description compensates well by explaining resolver_url, preset, and enable, including examples and the note that sfx, 360link, and primo require resolver_url. It maps to all three parameters and gives defaults for enable. Minor gaps: the preset 'test_free' from the schema is not documented, and the description does not state whether preset and resolver_url are mutually exclusive.

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 description clearly states a specific verb and resource: 'configure your institution's link resolver for full-text access' and 'This tool configures OpenURL link resolver integration.' It is distinct from most sibling tools by name and stated purpose, though it does not explicitly contrast itself with close siblings like test_institutional_access or diagnose_institutional_access.

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?

The description gives three concrete usage modes: preset, custom URL, and disable. It also provides an explicit boundary for remote callers: they may inspect with no arguments but cannot mutate server-owned deployment-wide settings, and should configure those at deployment time or from a trusted local server. It does not explicitly mention sibling tools like list_resolver_presets as alternatives, but the context is otherwise clear.

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

Deploy Server

Other Tools