Skip to main content
Glama

AY Grants

Get one grant

get_grant
Read-onlyIdempotent

One grant's page: status, funder, who can apply, place, amount, dates, the official sentences each field was read from, and the expected next round when there is one. A field we could not read is null, which means not confirmed. Counts as one row.

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": {
      "id": "<id>"
    },
    "name": "get_grant"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe id a search returned, such as us-360875, or the page address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare a read-only, idempotent, non-destructive, closed-world lookup, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: nulls mean "not confirmed" (not empty), it returns the official source sentences per field, it includes the expected next round only when one exists, and it "counts as one row," which matters for a row-oriented tool family.

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?

One dense sentence that is front-loaded with the resource and its field set, followed by two short clarifications on null semantics and row counting. Every clause carries information; the only cost is the run-on field list, which reads as one long enumeration.

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?

There is no output schema, so the description has to describe the return payload, and it does: it names the fields, explains null semantics, notes provenance text, conditional next-round data, and single-row shape. For a simple one-parameter lookup that is complete enough to call 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% and the single id parameter is fully documented there, including the alternate "page address" form. The description adds no further meaning about the id (format, casing, what happens on an unknown id), 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?

"One grant's page" plus an enumeration of the fields returned (status, funder, eligibility, place, amount, dates, provenance sentences, next round) makes it unmistakable that this is a single-record retrieval by id. It is distinguishable from the search/list siblings, whose names imply multi-row results, though the description never explicitly contrasts itself with them.

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

Usage Guidelines3/5

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

Usage is only implied: the schema's id description ("The id a search returned") and the phrase "Counts as one row" suggest this follows a search and returns a single row. The description itself gives no explicit when-to-use or when-not-to-use guidance versus screen_grants or search_open_grants.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources