Skip to main content
Glama
Sign In

Gondar

by io.github.FluxonLab
OverviewDiscussionsAdmin

Search open calls

search_open_calls
Read-onlyIdempotent

Search open grants, tenders, fellowships and other funding calls. Returns facts and the official link, from the first 50 rows of a list.

Input Schema

NameRequiredDescriptionDefault
sortNorelevance: best match first, the default with a query. deadline: soonest deadline first, the default without one. new: newest first. deadline and new apply even when a query is given.
typeNoOnly this kind of call. Without it, every kind.
limitNoDefault 10.
queryNoWords to search for, in any language.
offsetNoHow many rows to skip, to read the next page. Default 0.
regionNoComma-separated ISO country codes, or EU, UK or GLOBAL. GB is written UK. A country lists its own calls; add EU for EU-wide programmes.
languageNoLanguage for titles. A title comes translated only where Gondar has a translation (titleIsAutomaticTranslation); otherwise it stays in its source language, named in titleLanguage. Summaries always stay in the source language.
worldwideNoAlso include calls that declare worldwide eligibility.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / language / description
      Previous value: -"Language for translated titles. Without it, titles stay in the source language."New value: +"Language for titles. A title comes translated only where Gondar has a translation (titleIsAutomaticTranslation); otherwise it stays in its source language, named in titleLanguage. Summaries always stay in the source language."
    • changedInput schema / properties / sort / description
      Previous value: -"Soonest deadline first (default), or newest first."New value: +"relevance: best match first, the default with a query. deadline: soonest deadline first, the default without one. new: newest first. deadline and new apply even when a query is given."
    • changedInput schema / properties / sort / enum
      Previous value: -[
-  "deadline",
-  "new"
-]New value: +[
+  "relevance",
+  "deadline",
+  "new"
+]
  2. Changed2 schema fields changed
    • addedInput schema / properties / offset / description
      Added value: +"How many rows to skip, to read the next page. Default 0."
    • addedInput schema / properties / type / description
      Added value: +"Only this kind of call. Without it, every kind."
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover read-only, idempotent, closed-world, non-destructive behavior, so the bar is lower. The description adds that results include 'facts and the official link' and that results come 'from the first 50 rows of a list', which is genuinely extra context but is vague and sits awkwardly against an offset parameter with effectively no cap.

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?

Two short sentences, front-loaded with what is searched, then what is returned. The closing clause 'from the first 50 rows of a list' is slightly cryptic but not padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With eight all-optional, fully documented parameters and no output schema, the description should at least characterize the result shape and paging depth, and it does so only partially ('facts and the official link'). The 50-row statement is left unexplained relative to the large offset maximum, leaving an agent unsure how deep paging actually works.

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 description coverage is 100%, with detailed enum semantics for sort, type, region, and language, so the baseline of 3 applies. The description adds no parameter meaning beyond the schema and does not clarify the interaction between 'first 50 rows' and the offset/limit paging parameters.

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?

Specific verb (Search) plus a clear resource class (open grants, tenders, fellowships and other funding calls), and it states what comes back (facts and the official link). It does not name the sibling it differs from, notably get_open_call for single-record detail or list_saved_calls for the user's own list, so the differentiation is inferable rather than explicit.

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

Usage Guidelines2/5

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

The description gives no when-to-use or when-not guidance and names no alternatives, despite siblings such as get_open_call, list_my_matches, and list_saved_calls that an agent could easily confuse with this one. Usage is only implied by the verb 'Search'.

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

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