Skip to main content
Glama

Get a funding opportunity

get_opportunity
Read-onlyIdempotent

Fetch one Raise Lens grant or tender by its raiselens.com URL or id. Returns its title, summary, sectors, geography, deadline, amount, a link to the opportunity page and, where the opportunity page shows them, the funder, description, eligibility and key requirements.

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"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
idNoRaise Lens opportunity id.
ctaNoLink to the Raise Lens page that lists what each option includes.
urlNoThe opportunity page on raiselens.com.
typeNogrant, tender or subcontract.
foundYes
titleNo
accessNoLevel of detail in this record.
funderNoFunder or contracting authority.
sourceNoPublishing source.
sectorsNo
summaryNo
deadlineNoClosing date, YYYY-MM-DD, when published.
apply_urlNo
geographyNoCountries or regions, comma separated.
date_addedNoWhen Raise Lens added the record.
source_urlNoThe original listing at the source.
descriptionNoFull description, cut at 4,000 characters.
eligibilityNo
amount_displayNoFunding amount as published, or null when none is given.
key_requirementsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds one genuinely useful behavioral note — that funder, description, eligibility and key requirements appear only 'where the opportunity page shows them,' i.e. those fields are conditionally absent — but says nothing about failure modes for invalid ids or about auth/rate limits.

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?

Two sentences, the identifier scope is front-loaded, and the return-field list is compact. Nothing is redundant or padded.

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?

For a one-parameter lookup with a full output schema and complete annotations, the description covers the essential questions. The only meaningful omission is routing guidance versus get_opportunity_full.

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% for the single parameter, whose schema text ('A raiselens.com opportunity URL, or the opportunity id') is essentially restated in the description. No format examples, URL patterns, or error behavior for malformed ids are added, so this is baseline territory given the schema already does the work.

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?

The description opens with a specific verb and resource: 'Fetch one Raise Lens grant or tender by its raiselens.com URL or id,' which tells an agent exactly what the tool does and its single-item scope. It does not, however, distinguish itself from the sibling get_opportunity_full, leaving the agent to guess which variant to pick.

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 agent can infer this is the lookup-by-known-identifier tool (as opposed to search_opportunities or list_* tools), but the description never states when to use it, when not to, or why one would choose get_opportunity_full instead. No prerequisites or preconditions are mentioned.

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