Skip to main content
Glama

Compare the terms of two fund documents side by side

lpa_and_subscription_agreement
Read-onlyIdempotent

Side-by-side comparison of the terms of two fund documents: two limited partnership agreements (LPAs), or one fund's LPA and its subscription agreement. You read the documents and send the terms you found (fee, carry, hurdle, waterfall, clawback, removal, notice days, governing law and about 20 more, each a number or a fixed choice). Get back the terms side by side, which differ, which side is usually friendlier to the investor where that is clear, and, for an LPA plus subscription agreement, whether they agree and whether the investor representations fit the fund's stated exemptions (3(c)(7), Rule 506(c), the ERISA 25 percent test), with the sources and the date each rule was last amended, and a signed record. Set check_sources true to also ask the eCFR (official) whether any of those four rules was amended after the date this tool was written. Free. No model, nothing stored. It does NOT read documents, give legal or investment advice, or say a term is acceptable; do not send names, account numbers or document text.

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": {
      "a": "<a>",
      "b": "<b>"
    },
    "name": "lpa_and_subscription_agreement"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYes
bYes
check_sourcesNoAlso read the eCFR version history of the four rules and report any amendment after the reference date.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, yet the description still adds real value: 'Free. No model, nothing stored', an outbound eCFR lookup gated behind check_sources, and a 'signed record' in the response. It loses a point only because 'signed record' and the amendment-date comparison are not explained in any depth.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the body is a single dense run-on covering inputs, outputs, four regulatory rules, pricing, privacy and exclusions, which is hard to scan. Almost every clause carries information, yet it would read far better split into short labelled sentences.

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 three-parameter tool with deep nested term objects and no output schema, the description still tells the agent what comes back (differences, investor-friendliness, LPA-vs-subscription consistency, exemption-fit checks, sources, amendment dates, signed record) and what must not be sent. Residual gaps are the exact output shape and what happens when many terms are omitted.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Top-level schema coverage is thin (only check_sources carries a description), but the description compensates by naming representative terms ('fee, carry, hurdle, waterfall, clawback, removal, notice days, governing law and about 20 more') and their value shape ('each a number or a fixed choice'), which mirrors the nested enum/number schema. check_sources is explained in behavioural terms, not just repeated.

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?

Opens with a specific verb and resource: 'Side-by-side comparison of the terms of two fund documents', then bounds the scope precisely to 'two LPAs, or one fund's LPA and its subscription agreement'. An agent knows exactly what the tool does and what it will not do ('It does NOT read documents'), and no sibling tool overlaps this fund-document comparison space.

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?

Gives a clear precondition and workflow: the caller must read the documents itself and submit extracted terms, with an explicit exclusion list (no legal/investment advice, no 'acceptable' verdicts) and a data-handling rule (no names, account numbers, document text). It does not name any alternative tool, but the sibling list contains nothing comparable, so the routing gap is minor.

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