Skip to main content
Glama

cmbs.news: CMBS loan data

Tenant exposure

tenant_exposure
Read-onlyIdempotent

Lists the loans where a named tenant is among the three largest at the property, with balance, status, coverage and, where it is the largest tenant, the lease end. With no tenant it lists the tenants with the most CMBS exposure. Use it to measure exposure to one tenant; use search_loans with tenant set to filter a wider search. No match returns an empty list.

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

Input Schema

NameRequiredDescriptionDefault
limitNoTenants or loans listed: up to 25 without a key, 400 with one
tenantNoTenant name, e.g. "Walgreens", "Dollar Tree", "WeWork"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Tenants or loans listed: up to 25 free, 400 with a Pro or Team key"New value: +"Tenants or loans listed: up to 25 without a key, 400 with one"
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the bar is lower, but the description still adds real context: the fields returned, the conditional lease-end field only for the largest tenant, and the empty-list outcome on no match. It stops short of describing ordering or pagination of the result list, which keeps 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.

Conciseness5/5

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

Four short sentences, front-loaded with the primary mode, then the fallback mode, then routing guidance, then the empty-result edge case. No restated name or filler; every clause carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, yet the description enumerates the returned attributes and the conditional field, and it discloses the no-match behavior. For a two-parameter read-only lookup that is everything an agent needs to select and call it correctly.

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 baseline is 3, and the description goes beyond the schema by explaining what "tenant" actually measures (top-three tenant at the property) and what its absence does. The limit cap is only in the schema, not repeated here, but the added semantic meaning is genuine.

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 opens with a specific verb+resource ("Lists the loans where a named tenant is among the three largest at the property") and names the returned fields. It also states the second mode when no tenant is supplied, so the agent understands the tool is dual-purpose rather than a simple filter.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit use case ("measure exposure to one tenant") and an explicit alternative with its selection condition ("use search_loans with tenant set to filter a wider search"). The zero-argument behavior is also described, leaving nothing about when to call it to inference.

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