Skip to main content
Glama

Semerenko Group Public Site MCP

FX Hidden Cost

sem.ai_fx_hidden_cost_research
Read-only

Runs current web-backed AI research for the older Semerenko tool page: FX hidden-cost 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_fx_hidden_cost_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=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that the research is 'current' and 'web-backed', reinforcing live external retrieval, which is modestly useful beyond the openWorldHint flag. It does not disclose latency, cost, source attribution, or failure behavior for a web-dependent call.

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 short sentence with no padding, and the core 'runs current web-backed AI research' claim is front-loaded. The trailing 'for the older Semerenko tool page' clause is slightly muddled but does not bloat the definition.

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 seven-parameter, open-world research tool with no output schema, the description should say more about what comes back (e.g., research summary, sources, or structured cost breakdown). Instead it stops at a one-line topic label, leaving an agent unable to anticipate result shape or how the optional city/amount/currency/inputs values influence the research.

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 including the nested 'inputs' object are already documented in the schema. The description adds no parameter-level meaning such as how 'query' relates to 'inputs' or how 'forceFresh' interacts with the always-live behavior. Baseline 3 applies when the schema carries the load.

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 states a verb ('runs') and a topic ('FX hidden-cost AI research'), so an agent can infer this is a live research endpoint about FX hidden costs. However, the phrasing 'for the older Semerenko tool page' is vague and does not explain what an FX hidden-cost analysis actually covers or how it differs from siblings like sem.ai_swift_wire_cost_research or sem.ai_fx_break_even_research. The purpose is implied rather than sharply stated.

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 guidance on when to choose this tool over the many other sem.ai_*_research siblings. The only hint is the topic label 'FX hidden-cost', and no exclusions, prerequisites, or alternative-routing advice are given. An agent must infer usage purely from the name and topic keyword.

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