Skip to main content
Glama
Sign In

Ukri Gtr

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Gtr Search Organisations

gtr_search_organisations
Read-onlyIdempotent

Find UK universities, research institutes and companies that have received UKRI research funding, by institution name. Returns the GtR organisation id, official name, postcode and region — use the id with gtr_organisation_projects to list everything that institution was funded for.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "imperial college",
      "limit": 10
    },
    "name": "gtr_search_organisations"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesInstitution name or fragment, e.g. "imperial college", "rolls-royce".
pageNo1-based page. Default 1.
limitNoResults to return, 1-100. Default 10.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. The description adds that results include specific fields (id, name, postcode, region) and that the tool only returns UKRI-funded institutions. This is useful but not extensive; it does not contradict the annotations.

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 a single, front-loaded sentence with a clear action verb and a brief usage tip. Every word is essential, and there is no repetition or filler.

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?

No output schema exists, so the description must cover return values; it does so by listing the returned fields. It also explains the prerequisite (institution must have received UKRI funding) and suggests the next tool. With only 3 well-documented parameters, this is complete enough for an agent to use correctly.

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%, so baseline is 3. The description mentions 'institution name' for the name parameter, but the schema already provides a clear example and description. No additional semantic value beyond the schema.

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 starts with 'Find UK universities, research institutes and companies...by institution name.' It uses a specific verb (find) and resource (organisations), and the narrow scope (UKRI-funded institutions) clearly distinguishes it from sibling tools like gtr_search_projects or gtr_organisation_projects.

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 explicitly tells the agent to use the returned id with gtr_organisation_projects to get funded projects, providing a clear follow-up action. While it doesn't list when not to use this tool versus alternatives, the context is clear enough for typical search scenarios.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources