Skip to main content
Glama

fundz

by net.fundz
OverviewDiscussionsAdmin

Search agreements

search_agreements
Read-onlyIdempotent

Search for partnership agreements and strategic alliances. Filter by agreement type, company names, and date range.

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of days to look back (e.g., 7, 30, 60)
pageNoPage number, starting at 1 (default 1). Each page holds `limit` results; the reply ends with the total and next_page when there are more.
limitNoResults per page (default 20, max 50)
sinceNoOnly results Fundz added on or after this ISO date, e.g. "2026-10-01" (whole day, so a daily run may repeat that day). Overrides days. Use the date of your last run to get only what is new.
industryNoIndustry title, e.g. "Information Technology"
keywordsNoFree-text keywords matched against title/description (comma-separated for several)
locationNoCity, state or country title, e.g. "Texas"
company_nameNoFilter by company name
partner_nameNoFilter by partner company name
agreement_typeNoType of agreement (e.g., "Partnership", "Strategic Alliance", "Joint Venture")
new_since_last_pullNoOnly rows this account has not already been shown by an earlier new_since_last_pull call with the same filters. Fundz remembers per account and filter set, so a daily agent run gets just what is new, with no dates to track. The first call returns the normal window (days or since) and starts the marker. Ignores page: if more new rows are waiting the reply says so; call again the same way for the next batch. Needs a signed-in account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / new_since_last_pull
      Added value: +{
+  "description": "Only rows this account has not already been shown by an earlier new_since_last_pull call with the same filters. Fundz remembers per account and filter set, so a daily agent run gets just what is new, with no dates to track. The first call returns the normal window (days or since) and starts the marker. Ignores page: if more new rows are waiting the reply says so; call again the same way for the next batch. Needs a signed-in account.",
+  "type": "boolean"
+}
  2. Changed3 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results (default: 20)"New value: +"Results per page (default 20, max 50)"
    • addedInput schema / properties / page
      Added value: +{
+  "description": "Page number, starting at 1 (default 1). Each page holds `limit` results; the reply ends with the total and next_page when there are more.",
+  "type": "number"
+}
    • addedInput schema / properties / since
      Added value: +{
+  "description": "Only results Fundz added on or after this ISO date, e.g. \"2026-10-01\" (whole day, so a daily run may repeat that day). Overrides days. Use the date of your last run to get only what is new.",
+  "type": "string"
+}
  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 declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that — notably silent on the stateful behavior of new_since_last_pull (per-account markers, ignoring page) and on the signed-in account requirement, both of which are materially surprising behaviors.

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 the resource type and no filler. The brevity is appropriate, though it comes at the cost of coverage rather than being a model of efficient density.

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?

For an 11-parameter, no-output-schema search tool, the description is thin — it omits the stateful incremental-pull option and the auth requirement that an agent needs to call correctly. Combined with the rich schema it is workable, but not self-sufficient.

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%, so all 11 parameters are already documented in the schema; baseline is 3. The description touches only agreement type, company names, and date range, leaving industry, location, keywords, and the complex new_since_last_pull flag entirely to the schema.

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?

A clear verb-plus-resource statement: 'Search for partnership agreements and strategic alliances.' It distinguishes the resource well enough that an agent can separate it from siblings like search_acquisitions or search_funding_rounds without opening the schema, though it never names those siblings explicitly.

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 only says 'Filter by agreement type, company names, and date range' — that restates a subset of the parameters rather than telling the agent when to choose this tool over search_acquisitions or search_major_events. No exclusions, prerequisites, or guidance on which date filter (days vs since vs new_since_last_pull) to prefer.

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

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