Skip to main content
Glama

cmbs.news: CMBS loan data

What the trustee reports said about a loan

get_loan_servicer
Read-onlyIdempotent

Returns what each trust's monthly trustee report (Form 10-D) said about one loan, month by month, for about the last year: the special servicer's comment facts with a short excerpt, resolution strategy, transfer and return dates, foreclosure, bankruptcy and REO dates, appraisal values and reductions, advances and modifications, and what changed from the previous report. Use it after get_loan to see what happened to a loan and what changed this month. Without a key it returns a notice that a key is needed.

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": {
      "slug": "<slug>"
    },
    "name": "get_loan_servicer"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe loan slug: the last part of its cmbs.news URL, from search_loans

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world, non-destructive, so the bar is lower. The description still adds real value beyond them: a roughly one-year time horizon and, notably, the failure mode — without a key it returns a notice that a key is needed, which is a crucial auth behavior. It does not describe response shape or ordering, keeping it at 4.

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?

Front-loads the core purpose, then uses the enumeration to convey scope, and closes with the usage cue and auth caveat. The middle list of report fields is long but each item is a distinct data category, so it mostly earns its place; a tighter grouping would improve it.

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?

With no output schema, the description must convey what comes back, and it enumerates the report contents thoroughly (servicer comments with excerpts, resolution strategy, key dates, appraisals, advances, modifications, period-over-period changes). Combined with the auth caveat and the single well-documented parameter, an agent has everything needed to call it.

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 single parameter has 100% schema description coverage, including what the slug is and where to get it (search_loans), so the schema carries the load. The description only implies a single loan via "about one loan" and adds no syntax or format guidance beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb and resource — what each trust's monthly trustee report (Form 10-D) said about one loan, month by month — and names the source document type. That is far more specific than the title's vague phrasing and tells an agent exactly what data class it returns versus generic loan tools.

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?

Explicitly sequences the call: "Use it after get_loan to see what happened to a loan and what changed this month." That gives clear when-to-use context. It stops short of naming exclusions or distinguishing itself from plausible alternates like get_loan_history, so it is not a full 5.

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