Skip to main content
Glama
Sign In

Fundz

by io.github.Fund-z
OverviewDiscussionsAdmin

Benefit Plans in Play

get_benefit_plans_in_play
Read-onlyIdempotent

Recently funded companies (≤24 months) with a DOL Form 5500 benefit-plan filing on record: plan renewal timing, participant count vs current headcount ('outgrowing their plan'), and the incumbent insurance carrier from Schedule A. For benefits brokers, retirement-plan advisors, PEOs, HR-tech sellers. No API key required.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_benefit_plans_in_play"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoCompany name search
stateNo2-letter US state filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, and the description adds 'No API key required,' which covers auth expectations. It also adds data provenance and recency constraints (≤24 months, Form 5500, Schedule A) that annotations cannot convey. No contradiction exists.

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?

Two tightly written sentences with no filler. The data criteria lead, followed by intended audience and the auth note, so every sentence earns its place.

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 read-only tool with two optional, schema-documented parameters and no output schema, the description provides enough context: data source, recency window, key result fields, intended users, and auth. Minor omissions like pagination or ordering are acceptable for this simple use case.

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 already describes both optional parameters fully (company name search and state filter). The description's matching criteria relate to the dataset itself rather than parameter formats, so it adds no additional parameter semantics beyond 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?

The description specifies exactly what the tool surfaces: recently funded companies with DOL Form 5500 filings, including renewal timing, participant-count vs headcount comparison, and carrier from Schedule A. It names the target audience and data source, making it distinct from the sibling list tools. While it lacks an explicit 'returns' verb, the content is unambiguous.

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 target personas are explicitly listed—benefits brokers, retirement-plan advisors, PEOs, and HR-tech sellers—so an agent can infer when this list is relevant. It does not name sibling tools or give exclusion criteria, so it earns 4 rather than 5.

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