Skip to main content
Glama

Semerenko Group Public Site MCP

Source of Funds

sem.ai_source_of_funds_research
Read-only

Runs current web-backed AI research for the older Semerenko tool page: Source-of-funds 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_source_of_funds_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.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered elsewhere. The description adds that research is web-backed and current (reinforced by the forceFresh schema note), but says nothing about latency, cost, result format, or what "older page" implies for compatibility.

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 short sentence with no filler, which is good, but the phrase "older Semerenko tool page" consumes the only descriptive slot without conveying actionable meaning. Front-loading the verb is fine; the content budget is simply spent poorly.

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?

A seven-parameter research tool with a nested object and no output schema gets only one sentence, leaving return shape and expectations unexplained. For a live open-world research call, an agent needs more than a topic label to invoke it confidently.

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 coverage is 100% with all seven parameters documented in-schema, so the baseline is 3. The description adds no additional meaning about how query, inputs, or forceFresh interact for this particular research endpoint.

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 description names a specific action ("Runs current web-backed AI research") and ties it to a domain ("Source-of-funds AI"), which distinguishes it from the other sem.ai_*_research siblings by topic. However, "older Semerenko tool page" is opaque and the description never frames what a source-of-funds answer actually contains, so the agent must infer the resource.

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 when-to-use guidance, no preconditions, and no mention of when another sem.ai_*_research tool would be the better pick. The only implicit signal is the topic name, leaving routing between the many sibling research tools to inference.

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