Skip to main content
Glama

search_by_funder

Search for research records funded by a specific organization like NSF or European Commission, with optional query and sorting.

Instructions

Search for records funded by a specific organization.

Parameters

funder : str Funder name (e.g. "NSF", "European Commission", "NIH"). query : str, optional Additional search query. sort : str Sort order. page : int Page number. size : int Results per page.

Returns

list[dict] List of matching record summaries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
sizeNo
sortNobestmatch
queryNo
funderYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided; description covers parameters and return type but lacks details on constraints, rate limits, or side effects. For a read operation, it's minimally adequate.

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?

Structured with sections for Parameters and Returns, but the parameter list is verbose. Could be shortened without losing clarity.

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?

Output schema exists, so returns are sufficiently described as list of dicts. Input parameters are well-documented, making the tool usable for its intended purpose.

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?

Description adds examples for funder ('NSF', 'European Commission', 'NIH') and clarifies query as optional, going beyond the schema. Despite 0% schema coverage signal, it compensates well.

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?

Description clearly states 'Search for records funded by a specific organization' and distinguishes from siblings like search_by_community or search_by_license by focusing on the funder parameter.

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?

No explicit guidance on when to use this tool versus other search tools. It's implied for funder-specific queries, but no exclusions or alternatives mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Agostynah/Zenodo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server