Skip to main content
Glama

Semerenko Group Public Site MCP

Israel Mortgage Calculator

sem.ai_mortgage_research
Read-only

Runs current web-backed AI research for the older Semerenko tool page: Mortgage AI.

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": {
      "query": "<query>"
    },
    "name": "sem.ai_mortgage_research"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoOptional city or area hint.
queryYesCurrent scenario, question, calculator assumptions, listing text, or research request.
amountNoOptional amount, price, salary, transfer size, or budget.
inputsNoOptional structured calculator values already entered by the user.
pageUrlNoOptional Semerenko tool page URL.
currencyNoOptional currency hint.
forceFreshNoOptional freshness flag. This endpoint always runs live and does not return cached research content.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds that the research is 'current' and 'web-backed', consistent with openWorld, but it omits latency, cost, auth needs, and what the response contains.

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?

A single compact sentence with no filler, so it is appropriately sized. However, 'older Semerenko tool page' is low-value phrasing and the sentence could front-load the mortgage research scope more usefully.

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

Completeness2/5

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

For a 7-parameter research tool with a nested inputs object and no output schema, one sentence is thin. It does not explain what the research returns, how query/city/amount shape results, or whether pageUrl affects correctness.

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?

Schema description coverage is 100%, so all seven parameters already have descriptions. The main description adds no meaning about query, city, amount, inputs, pageUrl, currency, or forceFresh, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

It states a verb ('Runs ... AI research') and names 'Mortgage AI', so the general purpose is inferable. However, 'older Semerenko tool page' is opaque, and the description does not specify what mortgage research covers or distinguish it from the many sibling ai_*_research tools.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance. An agent cannot tell from the description whether to choose this over sem.ai_rental_yield_research, sem.ai_investment_simulator_research, or another research sibling; only the name hints at mortgage scope.

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