Skip to main content
Glama

Relendi — Commercial Real Estate Loan Tools

Ask a CRE Question

ask_cre_question
Read-only

Ask a plain-English question about commercial real estate lending and get a short answer grounded in Relendi's knowledge base, with citations. For loan math prefer size_loan or run_scenario, which are exact.

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": {
      "question": "<question>"
    },
    "name": "ask_cre_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, so the safety profile is covered. The description adds value beyond that: answers are short, grounded in a specific knowledge base, carry citations, and are not numerically exact for loan math. It does not discuss answer latency or what happens when the knowledge base lacks an answer, 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?

Two sentences, no filler. The capability and its output shape come first, and the routing caveat follows immediately after.

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?

There is no output schema, so the description correctly describes the return value (short answer with citations). For a single-parameter read-only Q&A tool this is nearly complete; it could have noted how to phrase a good question or what the 500-character ceiling implies, but nothing essential for correct invocation 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?

Only one parameter, and the schema documents it only as a constrained string (5-500 chars) with no descriptive text. The description supplies the missing semantics: the input is a natural-language, plain-English question scoped to commercial real estate lending, which tells the agent how to formulate it.

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 ("ask a plain-English question about commercial real estate lending") plus the response shape ("short answer grounded in Relendi's knowledge base, with citations"). That is enough for an agent to distinguish this knowledge-retrieval tool from the computational siblings named in the same sentence.

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?

Gives an explicit exclusion ("For loan math prefer size_loan or run_scenario, which are exact") alongside implicitly the positive case of open-ended conceptual questions. Both the when and the when-not are stated, with named alternatives and a reason (those tools are exact).

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