Skip to main content
Glama

Nihr

by io.github.pipeworx-io
OverviewAdmin

Nihr Get Award

nihr_get_award
Read-onlyIdempotent

Retrieve one UK NIHR award in full by its project id (either the modern form NIHR208893 or the older slash form 002/0028). Returns the plain-English abstract and the scientific abstract, award value in GBP, programme, funding stream and status, start and end dates, the contracted organisation with postcode and latitude/longitude, HRCS and UKCRC health-category coding, the fundingawards.nihr.ac.uk record link, and every named award holder with their ORCID and role. Use when an agent has an NIHR project reference and needs the detail behind it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesNIHR project id exactly as published, e.g. "NIHR208893", "002/0028" or "DRF-2009-02-122". Slashes are handled.

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: -[
-  {
-    "project_id": "002/0028"
-  }
-]New value: +[
+  {
+    "project_id": "NIHR205461"
+  }
+]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already indicate the tool is read-only, idempotent, and non-destructive. The description supplements this by detailing exactly what data is returned (abstracts, award value, coding, etc.), providing complete transparency about the tool's behavior beyond 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, dense paragraph that front-loads the primary action and then enumerates return fields. Every sentence adds value, with no filler. It is appropriately sized for the complexity of the tool.

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?

With a single parameter, full schema coverage, comprehensive annotations, and no output schema, the description covers everything needed for agentic use: what the tool does, what input is expected, and what output is returned. No gaps remain.

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

Parameters4/5

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

Schema coverage is 100%, so the description's contribution over the schema is modest but meaningful. It explains the two forms of the project id (modern NIHR208893 and older slash form) and notes that slashes are handled, adding practical context beyond the schema's description.

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 uses specific verbs ('Retrieve') and a clear resource ('one UK NIHR award in full by its project id'). It also distinguishes the tool from siblings by specifying the exact identifier formats and the depth of information returned (abstracts, awards details, etc.). This makes the purpose highly clear.

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 states when to use the tool: 'Use when an agent has an NIHR project reference and needs the detail behind it.' While it does not mention when not to use or name alternatives, the context is clear given the sibling tools like nihr_search_awards. It provides sufficient guidance for typical usage.

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

All Nihr 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