Skip to main content
Glama

FundingTracker

Get a funder profile

get_funder
Read-onlyIdempotent

Get one funder's public profile from the FundingTracker directory by slug: financing type, description, website, its listed facts (type, max deal, payment schedules, ISO brokers, states), average merchant rating, review count and the most recent public reviews.

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": {
      "slug": "<slug>"
    },
    "name": "get_funder"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesFunder slug from search_funders (e.g. 'apex-funding-group-llc') or its fundingtracker.app/funders URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds useful behavioral context by disclosing that the profile is public and enumerating what it contains (facts, ratings, recent reviews), which helps the agent judge whether one call is sufficient. It doesn't mention truncation of reviews or error behavior for unknown slugs, keeping it below a 5.

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?

It is a single front-loaded sentence with the resource and lookup key first, followed by the field inventory. Slightly dense with its parenthetical fact list, but every element informs the agent about what it gets back.

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?

There is no output schema, so the description's enumeration of returned fields is doing real work and largely compensates. For a one-parameter read-only lookup this is close to complete; only edge behavior (unknown slug, review pagination) is unaddressed.

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% and the single slug parameter is thoroughly documented in the schema, including an example and its origin ('from search_funders' or the fundingtracker.app URL). The description adds only the phrase 'by slug', matching the baseline of 3 when the schema does the heavy lifting.

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 names a specific verb and resource ('Get one funder's public profile from the FundingTracker directory') and immediately distinguishes itself from the sibling search_funders by specifying a single-fund lookup keyed by slug. It even enumerates the returned profile components, so an agent knows exactly what this tool yields.

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?

'Get one funder ... by slug' implies this is the detail lookup whose prerequisite slug comes from search_funders, but the description itself never states when to use this versus search_funders or what to do if the slug is unknown. Usage is implied rather than explicit; the routing detail lives in the schema's slug description, not the tool description.

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