Skip to main content
Glama

Get a funding opportunity with full details

get_opportunity_full
Read-onlyIdempotent

Fetch one Raise Lens grant or tender by URL or id as a full record: funder, description, eligibility, key requirements, source, apply link and the raiselens.com page.

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": {
      "url_or_id": "<url_or_id>"
    },
    "name": "get_opportunity_full"
  }
}

Input Schema

NameRequiredDescriptionDefault
url_or_idYesA raiselens.com opportunity URL, or its id.

Output Schema

NameRequiredDescriptionDefault
idNo
urlNoThe opportunity page on raiselens.com.
typeNogrant, tender or subcontract.
foundYes
titleNo
accessNo
funderNoFunder or contracting authority.
sourceNoPublishing source.
sectorsNo
summaryNo
deadlineNo
apply_urlNo
geographyNo
date_addedNoWhen Raise Lens added the record.
source_urlNoThe original listing at the source.
descriptionNoFull description, cut at 4,000 characters.
eligibilityNo
amount_displayNo
key_requirementsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the description need not repeat it. It adds a field-level inventory of the record (funder, eligibility, requirements, apply link), which is genuinely informative behavior-wise, but says nothing about not-found handling, staleness, or whether the returned record is a live or cached snapshot.

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?

A single front-loaded sentence with the action and scope first, followed by a compact field list. The enumeration of return fields is slightly listy and partly redundant with the output schema, but nothing is padded or wasted.

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?

The tool is simple (one required parameter, no nesting), an output schema exists, and annotations cover the behavioral contract, so the description need not explain return values or safety. The only meaningful gap left is routing guidance against the sibling summary tool, which keeps it from a 5.

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 the single parameter is already fully documented, and the description only restates the same 'URL or id' duality. No extra meaning such as accepted URL forms, bare-id format, or prefix handling is added beyond 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?

"Fetch one Raise Lens grant or tender ... as a full record" gives a specific verb, a specific resource, and a cardinality constraint (exactly one). The word "full" implicitly contrasts with the sibling get_opportunity, but it never names that sibling, so the differentiation is left to inference.

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: "full record" suggests this is the heavyweight variant to pick when summary data is insufficient, and "by URL or id" hints at a lookup workflow. There is no explicit statement of when to prefer get_opportunity or search_opportunities instead, and no note about what happens if the identifier does not resolve.

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