Skip to main content
Glama
FundFluent

FluentLab Funding Assistant

by FundFluent
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

FluentLab Funding Assistant MCP Server

NPM Downloads NPM License

MCP Server for the FluentLab's Funding Assistant API.

Tools

  1. get-funding-options

    • Get available funding options

    • Optional inputs:

      • limit (number, default: 10, max: 100): Maximum number of funding options to return

      • page (number): Page number to retrieve

    • Returns: List of funding options with their ids, name, description, slug and information

  2. get-document-checklist-for-funding-programme

    • Get the required documents to apply for a funding programme

    • Required inputs:

      • slug (string): Unique slug defined by FluentLab for a funding option

    • Returns: List of required documents to apply for a funding programme

Related MCP server: grants-gov

Setup

Installing via Smithery

To install funding-assistant for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @fundfluent-admin/funding-assistant --client claude

Usage with Claude Desktop

Add the following to your claude_desktop_config.json:

npx

{
  "mcpServers": {
    "funding-assistant": {
      "command": "npx",
      "args": [
        "-y",
        "@fundfluent/funding-assistant"
      ]
    }
  }
}

Troubleshooting

License

This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.

Available Tools

1 tool
get-funding-optionsGet Funding OptionsA
Read-onlyIdempotent

Retrieve available funding opportunities with detailed information including name and description. Use this tool when users need to explore available grants, funds, or financing opportunities. The results include program names, descriptions, eligibility criteria, and application details.

ParametersJSON Schema
NameRequiredDescriptionDefault
limitYes
pageYes

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false, covering key behavioral traits. The description adds context about the type of data returned ('program names, descriptions, eligibility criteria, and application details'), which is useful but doesn't provide rich behavioral details like rate limits or error handling.

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?

The description is concise and well-structured: three sentences that efficiently cover purpose, usage, and result details without redundancy. Each sentence adds clear value, making it front-loaded and easy to parse.

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?

Given the tool's moderate complexity (read-only search with two parameters), annotations cover safety and idempotency, and the description explains purpose, usage, and result content. However, without an output schema, the description could benefit from more detail on return format or pagination, though it's largely complete for its context.

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?

The input schema fully documents the two parameters (limit and page) with types and constraints, but schema description coverage is 0%. The description doesn't mention parameters at all, so it adds no semantic value beyond the schema. Baseline 3 is appropriate since the schema handles parameter documentation.

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 clearly states the tool's purpose: 'Retrieve available funding opportunities with detailed information including name and description.' It specifies the verb ('retrieve'), resource ('funding opportunities'), and scope ('detailed information'), though it doesn't differentiate from siblings as none exist.

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

Usage Guidelines4/5

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

The description provides explicit usage guidance: 'Use this tool when users need to explore available grants, funds, or financing opportunities.' This clearly indicates when to use the tool, but since there are no sibling tools, it doesn't specify alternatives or exclusions.

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

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.6/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools, as there are no other tools to compare or misselect against. The tool's purpose is clearly defined and distinct by default.

Naming Consistency5/5

Since there is only one tool, it inherently follows a consistent naming pattern with itself. The tool name uses kebab-case (get-funding-options), which is a clear and readable convention, and there are no other tools to create inconsistency.

Tool Count2/5

A single tool is too few for a server named 'FluentLab Funding Assistant', which implies a broader scope of funding-related operations. This minimal set suggests significant gaps in functionality, such as creating, updating, or managing funding applications, making it under-scoped for the apparent purpose.

Completeness1/5

The tool set is severely incomplete for a funding assistant domain. It only provides retrieval of funding options, lacking essential operations like applying for funding, tracking applications, updating details, or managing user profiles, which are critical for a comprehensive funding workflow.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • bandiradar-mcp

    mayai-it
    A
    license
    B
    quality
    A
    maintenance
    Enables monitoring Italian public funding opportunities, normalizing them into a canonical model, and ranking them against a company profile with a two-stage matcher.
    6
    2
    MIT

  • grants-gov

    pipeworx-io
    A
    license
    Not graded
    quality
    C
    maintenance
    Provides access to open federal grant opportunities from Grants.gov without authentication. Enables querying and exploring grant data through natural language via Pipeworx gateway.
    6
    MIT

  • EUACC EU Funding MCP Connector

    caraulani
    A
    license
    Not graded
    quality
    C
    maintenance
    Provides AI assistants with real-time, verified European funding data including open grant calls, programmes, consortium partners, VCs, and incubators, enabling natural language queries about EU funding.
    MIT
  • @pipeworx/eu-funding-tenders by pipeworx-io

    @pipeworx/eu-funding-tendersofficial

    pipeworx-io
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables searching and retrieving detailed information on EU grant calls and tenders from the EU Funding & Tenders Portal, including deadlines, budgets, and topic details.
    8
    MIT

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/FundFluent/funding-assistant'

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