Skip to main content
Glama

Semerenko Group Public Site MCP

Israel Investment Simulator

sem.ai_investment_simulator_research
Read-only

Runs current web-backed AI research for the older Semerenko tool page: Investment simulator 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_investment_simulator_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.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so "web-backed" and "current" are largely redundant with openWorldHint. The description adds nothing about latency, cost, output shape, or how the live web research is synthesized, and the one genuinely useful behavioral fact (always live, never cached) lives only in the forceFresh schema property, not the description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

It is a single front-loaded sentence with no padding, but "for the older Semerenko tool page" consumes a third of the text while conveying little to an agent. Brevity here reflects under-specification rather than disciplined editing.

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?

Seven parameters including a nested structured-values object and no output schema is a fairly complex surface, yet the description never explains what kind of research result comes back or how `query` versus `inputs` should be populated. For a live AI-research endpoint where output varies, the absence of any return-value characterization is a real gap.

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 every one of the 7 parameters (including the nested `inputs` object) is already documented in the schema. The description adds no meaning beyond it, which is acceptable given full coverage but earns only the baseline.

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?

The verb and resource are stated ("Runs current web-backed AI research" for an investment simulator), which separates it topically from the fx/mortgage/rental-yield research siblings. However, the qualifier "for the older Semerenko tool page" is opaque and does not clarify scope; it reads as internal shorthand rather than a description of what the tool produces.

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 guidance, no when-not-to-use guidance, and no routing to alternatives among the many ai_*_research siblings. An agent must infer from the topic word "investment simulator" alone that this is the right research endpoint for portfolio/investment-scenario questions.

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