Skip to main content
Glama

Ukri Gtr

by io.github.pipeworx-io
OverviewAdmin

Gtr Search Publications

gtr_search_publications
Read-onlyIdempotent

Search journal articles, books and conference papers that UKRI grant holders reported as outcomes of their funded work. Returns title, authors, journal, publication date, DOI, PubMed id, ISSN and the GtR id of the project that produced it — the way to trace UK public research funding through to what it published.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page. Default 1.
limitNoResults to return, 1-100. Default 10.
queryYesFree text over publication titles and abstracts, e.g. "graphene battery".
search_fieldNoWhich field the query text is matched against. Default "all".

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "limit": 3,
-    "query": "graphene battery"
-  }
-]New value: +[
+  {
+    "limit": 10,
+    "query": "graphene battery"
+  }
+]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, etc. The description adds context by listing returned fields (title, authors, journal, DOI, etc.) and the GtR project ID, which helps an agent understand the output beyond what annotations cover.

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 two sentences: the first clearly states the purpose, the second lists return fields. It is front-loaded, concise, and every sentence adds value.

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?

Despite no output schema, the description sufficiently explains the return values (title, authors, journal, etc.) and the GtR project ID for tracing. Combined with clear input schema and annotations, the description is complete for an agent to use the tool effectively.

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%, with clear descriptions for all parameters. The description does not add new information about parameter usage beyond what the schema already provides, meeting the baseline for high coverage.

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?

The description clearly states it searches journal articles, books, and conference papers reported as UKRI grant outcomes. The verb 'Search' and resource 'publications' are specific, and it distinguishes itself from sibling tools like gtr_search_projects by focusing on publications linked to funding.

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 implies usage for finding UKRI-funded publications and explains the value of the GtR project ID for tracing funding. However, it does not explicitly state when not to use this tool or compare it directly to siblings.

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

All Ukri Gtr toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources