Skip to main content
Glama
u9401066

pubmed-search-mcp

by u9401066
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

test_institutional_access

Read-onlyIdempotent

Verify your institutional link resolver is configured, reachable, and returning valid responses. Test with a PMID to confirm network access and generated OpenURL before retrieving full text.

Instructions

Test your institutional link resolver configuration.

═══════════════════════════════════════════════════════════════════════════════ 🧪 TEST INSTITUTIONAL ACCESS ═══════════════════════════════════════════════════════════════════════════════

Tests if your configured link resolver is:

  1. Properly configured

  2. Reachable (network connection)

  3. Returns a valid response

NOTE: This only tests if the resolver endpoint is reachable. Actual full-text access depends on your institution's subscriptions.

═══════════════════════════════════════════════════════════════════════════════ FREE TEST OPTIONS: ═══════════════════════════════════════════════════════════════════════════════

If you don't have institutional access, you can test with:

  1. Use "test_free" preset (EBSCO public resolver): configure_institutional_access(preset="test_free") test_institutional_access()

  2. Most university resolvers will respond even without VPN, they just won't provide full-text (shows "Access options" page)

Args: pmid: PMID to use for testing (default: 38353755)

Returns: Test results including: - Configuration status - Network reachability - Generated OpenURL - Link to test manually

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pmidNoComplete identifier string; optional identifier prefix, official article URL, or inline backticks. No numbers, foreign hosts, URL queries/fragments or partial identifiers.38353755

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.7.7
    • addedInput schema / properties / pmid / description
      Added value: +"Complete identifier string; optional identifier prefix, official article URL, or inline backticks. No numbers, foreign hosts, URL queries/fragments or partial identifiers."
    • addedInput schema / properties / pmid / examples
      Added value: +[
+  "33053718",
+  "PMID:33053718",
+  "https://pubmed.ncbi.nlm.nih.gov/33053718/"
+]
    • addedInput schema / properties / pmid / format
      Added value: +"pubmed-pmid"
    • changedInput schema / properties / pmid / maxLength
      Previous value: -32New value: +512
    • addedInput schema / properties / pmid / x-pubmed-input
      Added value: +"pmid"
  2. Changed4 schema fields changedv0.7.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / pmid / maxLength
      Added value: +32
    • addedInput schema / properties / pmid / minLength
      Added value: +1
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "test_institutional_accessOutput",
-  "type": "object"
-}New value: +null
  3. First observedv0.5.16

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful scope-limiting context beyond that: it only tests endpoint reachability, actual full-text depends on subscriptions, and a resolver may respond without VPN while still not serving full text.

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

Conciseness2/5

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

The content is useful, but it is wrapped in large ASCII banner blocks with repeated separators, producing substantial visual noise for what amounts to a few sentences. Front-loading is fine, but the decoration is not earning its place.

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 single-parameter, read-only test tool, the definition supplies purpose, scope caveats, a return-value outline, and setup guidance. That is complete enough for correct invocation; the only real omission is how it relates to the sibling diagnostic tool.

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?

Only one parameter and schema description coverage is 100%, so the schema carries the semantic load (format, examples, length limits). The description merely restates the pmid default (38353755), adding essentially nothing beyond what the schema already states.

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 states a specific verb (test) and resource (institutional link resolver configuration) and enumerates what is being checked: configuration, reachability, and response validity. It does not, however, distinguish itself from the sibling diagnose_institutional_access, which appears to cover very similar ground.

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 FREE TEST OPTIONS section gives clear situational guidance: if you lack institutional access, call configure_institutional_access(preset="test_free") first, and it notes most university resolvers respond without VPN. That is real when-to-use context, though it never contrasts with the sibling diagnose_institutional_access tool.

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