Skip to main content
Glama
wos-mcp-bridge

wos-mcp-bridge

Search

search
Read-onlyIdempotent

Retrieve the first 10 relevant Web of Science Core Collection records using advanced query syntax, returning each record's ID, title, and URL.

Instructions

Return the first 10 WoS records by relevance using advanced syntax.

Example: TS=(canine AND lung). Each result has id, title and url. Use fetch for bibliographic metadata, not the article full text.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWoS advanced search across available Core Collection disciplines; no control characters.

Output Schema

NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds behavior beyond that: a hard cap of 10 results and relevance-based ordering, which tells the agent results may be truncated and ranked rather than exhaustive.

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?

Front-loaded with the core behavior, then the example, then the handoff to fetch — no filler sentences. The line 'Each result has id, title and url' is mildly redundant given an output schema exists, a small amount of unearned space.

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?

For a one-parameter search tool with full schema coverage, complete annotations and an output schema, the description covers syntax, result count, ranking, and the natural next step. 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the parameter already documents WoS advanced syntax with its own examples. The description's 'TS=(canine AND lung)' example illustrates the field-tag form but adds little the schema does not already supply, so the baseline of 3 applies.

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?

States a specific verb+resource ('Return the first 10 WoS records by relevance') with the result cap and ordering made explicit, which an agent can act on directly. It does not differentiate against the other search siblings (search_wos, search_literature), so it stops short of a 5.

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 'Use fetch for bibliographic metadata, not the article full text' sentence establishes the search-then-fetch workflow and marks the boundary of this tool's job. It gives clear context but no explicit when-not for this tool versus the other search variants.

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