Skip to main content
Glama

CRE Capital: capital stack calculator

Who provides each capital stack layer

list_capital_providers
Read-onlyIdempotent

Names of firms in the business of each layer, only as the institutions publish them: Fannie Mae DUS lenders and Freddie Mac Optigo lenders (senior agency multifamily debt) and public mortgage REITs that hold mezzanine loans or preferred equity per their 10-Qs. Filter by list or by part of a name. Being on a list does not mean a firm will quote a given deal.

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": "list_capital_providers"
  }
}

Input Schema

NameRequiredDescriptionDefault
listNoWhich published list. Default all.all
nameNoOptional part of a firm name to look for, e.g. "Walker" or "Arbor".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world lookup. The description adds useful behavioral context by stating the data is limited to what institutions publish and that list membership does not guarantee deal participation, though it does not mention pagination or exact return shape.

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?

The description is front-loaded with the core resource definition and follows with filtering and caveat information. It is dense but every sentence contributes; minor redundancy with the fully documented schema keeps it from being maximally concise.

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 two-parameter lookup with rich annotations and no output schema, the description covers the resource, data provenance, filtering, and a key limitation. It could be slightly more complete by specifying the return structure or ordering, but nothing essential is missing.

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?

Schema coverage is 100%, so the baseline is 3. The description goes further by explaining what the list categories represent and clarifying that the name filter matches only part of a firm name, adding meaning beyond the enum and schema descriptions.

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 uses a specific verb and resource: it returns firm names for each capital-stack layer, sourced from named institutional lists. It clearly distinguishes this from the sibling capital_stack and get_capital_costs tools by focusing on provider identity rather than stack structure or pricing.

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?

It states how to use the filters (by list or by part of a name) and adds an important caveat that inclusion does not imply a firm will quote a given deal. It does not explicitly compare when to use this tool versus capital_stack or get_capital_costs, so it falls short of full alternative guidance.

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