Skip to main content
Glama
leandrogavidia

Marinade Finance MCP Server

Search Marinade Finance Documentation

search_documentation

Search Marinade Finance documentation to find information, code examples, API references, and guides for Solana liquid staking operations.

Instructions

Search across the documentation to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Marinade Finance Docs, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe search query string

Implementation Reference

  • The asynchronous callback function that executes the 'search_documentation' tool. It proxies the query to a remote MCP client's 'searchDocumentation' tool and formats the response.
    callback: async ({ query }: { query: string }) => {
        try {
            const marinadeFinanceDocsMcpClient = await createMarinadeFinanceDocsMcpClient();
    
            const response = await marinadeFinanceDocsMcpClient.client.callTool({ name: "searchDocumentation", arguments: { query } })
    
            return {
                content: [
                    {
                        type: "text",
                        text: JSON.stringify(response, null, 2),
                    },
                ],
            };
    
        } catch (err) {
            const isAbort = (err as Error)?.name === "AbortError";
    
            return {
                content: [
                    {
                        type: "text",
                        text: JSON.stringify(
                            {
                                error: isAbort ? "Request timed out" : "Failed to fetch documentation",
                                reason: String((err as Error)?.message ?? err),
                            },
                            null,
                            2
                        ),
                    },
                ],
            };
        }
    }
  • Zod-based input schema for the 'search_documentation' tool, defining the required 'query' parameter.
    inputSchema: {
        query: z.string().describe("The search query string"),
    },
  • src/server.ts:25-42 (registration)
    Registration of the 'search_documentation' tool (via loop over marinadeFinanceTools) to the MCP server, including schema and handler wrapper.
    for (const t of marinadeFinanceTools) {
        server.registerTool(
            t.name,
            {
                title: t.title,
                description: t.description,
                inputSchema: t.inputSchema
            },
            async (args) => {
                const result = await t.callback(args);
                return {
                    content: result.content.map(item => ({
                        ...item,
                        type: "text" as const
                    }))
                };
            }
        );
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that the search 'returns contextual content with titles and direct links to the documentation pages', adding useful behavioral context about the output format. However, it doesn't mention potential limitations like search scope, result 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 efficiently structured in two sentences: the first defines the tool's purpose and scope, the second provides usage guidelines and output details. Every sentence adds value with zero wasted words, 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?

For a simple search tool with one parameter and no output schema, the description is largely complete—it covers purpose, usage, and output behavior. The gap is the lack of annotations, which leaves some behavioral aspects (e.g., idempotency, error cases) unspecified, but overall it provides sufficient context for effective use.

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% for the single parameter 'query', which is documented as 'The search query string'. The description adds no additional parameter semantics beyond what the schema provides, so the baseline score of 3 is appropriate.

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?

The description clearly states the verb 'search' and resource 'Marinade Finance documentation', specifying it finds 'information, code examples, API references, and guides'. It distinguishes from sibling tools (e.g., get_marinade_state, stake_msol) by focusing on documentation search rather than state queries or transactions.

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

Usage Guidelines5/5

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

It explicitly states when to use this tool: 'when you need to answer questions about Marinade Finance Docs, find specific documentation, understand how features work, or locate implementation details'. This provides clear context for usage without alternatives needed, as no other documentation tools exist among siblings.

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/leandrogavidia/marinade-finance-mcp-server'

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