Skip to main content
Glama
u9401066

pubmed-search-mcp

by u9401066
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

configure_institutional_access

DestructiveIdempotent

Configure your institution's OpenURL link resolver to access paywalled articles via library subscriptions using a preset or custom resolver URL.

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. Changed3 schema fields changedv0.7.7
    • addedInput schema / properties / enable / anyOf
      Added value: +[
+  {
+    "default": true,
+    "title": "Enable",
+    "type": "boolean"
+  },
+  {
+    "description": "Explicit true/false text, ignoring ASCII case and surrounding whitespace.",
+    "pattern": "^[ \\t\\r\\n]*(?:[tT][rR][uU][eE]|[fF][aA][lL][sS][eE])[ \\t\\r\\n]*$",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / enable / type
      Removed value: -"boolean"
    • changedInput schema / properties / preset / anyOf
      Previous value: -[
-  {
-    "enum": [
-      "ntu",
-      "ncku",
-      "nthu",
-      "nycu",
-      "harvard",
-      "stanford",
-      "mit",
-      "yale",
-      "oxford",
-      "cambridge",
-      "sfx",
-      "360link",
-      "primo",
-      "test_free"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "anyOf": [
+      {
+        "enum": [
+          "ntu",
+          "ncku",
+          "nthu",
+          "nycu",
+          "harvard",
+          "stanford",
+          "mit",
+          "yale",
+          "oxford",
+          "cambridge",
+          "sfx",
+          "360link",
+          "primo",
+          "test_free"
+        ],
+        "type": "string"
+      },
+      {
+        "pattern": "^[ \\t\\r\\n]*(?:[nN][tT][uU]|[nN][cC][kK][uU]|[nN][tT][hH][uU]|[nN][yY][cC][uU]|[hH][aA][rR][vV][aA][rR][dD]|[sS][tT][aA][nN][fF][oO][rR][dD]|[mM][iI][tT]|[yY][aA][lL][eE]|[oO][xX][fF][oO][rR][dD]|[cC][aA][mM][bB][rR][iI][dD][gG][eE]|[sS][fF][xX]|360[lL][iI][nN][kK]|[pP][rR][iI][mM][oO]|[tT][eE][sS][tT]_[fF][rR][eE][eE])[ \\t\\r\\n]*$",
+        "type": "string"
+      }
+    ]
+  },
+  {
+    "type": "null"
+  }
+]
  2. 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
  3. First observedv0.5.16

TDQS

A4.2/5.0
Behavior4/5

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

Adds real behavioral context beyond annotations: remote service callers may call with no arguments to inspect operator-installed config but cannot mutate server-owned deployment-wide OpenURL settings, and enable defaults to True. It also discloses idempotence implicitly via the preset/config model. It doesn't spell out the full destructive implications for existing config, keeping it at 4.

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 purpose is front-loaded, but the body is padded with ASCII-art banners and a multi-step 'how link resolvers work' explanation that an agent doesn't need to select or invoke the tool. Several sentences could be cut without losing invocation-relevant information.

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 zero-required-parameter mutation tool with no output schema, the description covers the key risks (server-owned settings, remote vs local mutation), the option space, and default behavior. It leaves the exact returned configuration status format vague, but the rest is complete enough to call correctly.

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 compensate, and it does: the Args section plus usage examples explain resolver_url, preset (with the full preset list), and enable/disable semantics. It's strong compensation, though it doesn't note the enum values embedded in the schema pattern or URL length limit.

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 (configure) and resource (institution's OpenURL link resolver for full-text access), and immediately clarifies the integration type and its purpose. An agent can distinguish this from siblings like diagnose_institutional_access or test_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?

Explicitly lays out three usage modes (preset, custom URL, disable) with example invocations, and notes that remote callers can inspect but not mutate deployment-wide settings. It doesn't explicitly name sibling alternatives such as list_resolver_presets or diagnose_institutional_access for related tasks, 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.

Deploy Server

Other Tools