journal-scout-mcp

scival_institution_lookup

Find academic institutions by name in SciVal and retrieve matching institution IDs and metrics for research evaluation.

Instructions

SciVal institution lookup by name.

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": "scival_institution_lookup"
  }
}

Input Schema

Name	Required	Description	Default
`count`	No
`query`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Sep 25, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states only 'lookup,' which implies a read operation, but does not mention matching behavior, pagination, rate limits, or what the response contains.

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?

The description is six words and contains no filler. The resource is front-loaded and every word contributes meaning. It is extremely concise, even if additional context would be helpful elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and no annotations, the description is too thin to fully support correct invocation. It does not indicate whether the result is a list, an ID, or a full institution profile, nor does it explain how this relates to scival_institution_metrics. An agent may be uncertain how to use the result in downstream calls.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 for the undocumented parameters. It clarifies that 'query' is an institution name, but it does not explain the 'count' parameter or its default behavior. This is only minimal added meaning over the schema.

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 resource (SciVal institutions) and operation (lookup by name), which distinguishes it from author lookup and metrics tools. However, 'lookup' is somewhat generic and does not clarify what the returned data represents.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus scival_author_lookup, scival_institution_metrics, or search_all. 'By name' is an implicit hint, but no explicit context, prerequisites, or alternative routing is provided.

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

Deploy Server