Skip to main content
Glama

Semerenko Group Public Site MCP

List Semerenko real-estate calculators

sem.list_calculators
Read-only

Lists all public Semerenko Group real-estate calculators and tools (mortgage, seller net proceeds, rental yield, investment simulator, transfer costs, compliance helpers, investment score) with their page URLs and whether live AI research is wired.

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": "sem.list_calculators"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context by stating that each entry carries its page URL and a flag for whether live AI research is wired, which is the key signal an agent needs before selecting a follow-up tool. It stops short of saying the catalog is curated/static, which would have made this 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?

A single well-formed sentence that front-loads the action and resource, then packs the enumeration and the returned fields into the same clause. No filler, no restatement of the title.

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, and the description compensates by naming the two per-entry fields (page URL and live-AI-research flag) an agent will receive. For a zero-parameter listing tool this is close to complete; only a note about ordering, count, or how often the catalog changes would close the remaining gap.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. Schema coverage is reported as 100% with an empty properties object, consistent with a no-argument call.

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

Purpose4/5

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

The description gives a specific verb ("Lists") and resource ("all public Semerenko Group real-estate calculators and tools") and enumerates the categories covered (mortgage, rental yield, transfer costs, etc.), so the scope is unambiguous. It does not, however, contrast itself with catalog-adjacent siblings such as sem.get_tool_inventory or the individual sem.calc_* and sem.ai_* tools, leaving that distinction to inference.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can reasonably infer this is a discovery call to run before invoking a specific calculator or AI research tool. There is no explicit statement of when to prefer this over sem.get_tool_inventory, nor any exclusion or prerequisite noted.

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