Skip to main content
Glama

Semerenko Group Public Site MCP

SWIFT Wire Cost

sem.ai_swift_wire_cost_research
Read-only

Runs current web-backed AI research for the older Semerenko tool page: SWIFT 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_swift_wire_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, openWorldHint, and destructiveHint=false, so safety is covered. The description does add that research is 'current' and 'web-backed', implying live retrieval rather than stored data, but it says nothing about latency, cost, failure modes, or the shape of the returned research. The schema's forceFresh note carries the 'always live, never cached' detail, 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.

Conciseness4/5

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

It is a single short sentence with the verb front-loaded and no filler. The phrasing 'the older Semerenko tool page: SWIFT cost AI' is awkward and internally referential, but nothing is padded or redundant.

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?

With seven parameters, a nested object, and no output schema, the description should explain what kind of result comes back from an AI research call. Instead it stops at the topic, leaving the agent to guess whether the response is prose, structured figures, or citations, and offering no hint about how the optional city/amount/currency hints influence results.

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% across all seven parameters, so every field including the nested 'inputs' object and the always-live 'forceFresh' flag is already documented. The description adds no additional meaning about how query, amount, city, or currency shape the research request, so the baseline of 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?

The description names a specific verb and resource: 'Runs current web-backed AI research' for 'SWIFT cost'. However, 'the older Semerenko tool page: SWIFT cost AI' is vague internal shorthand, and the phrase does not distinguish this tool from similarly shaped siblings such as sem.ai_fx_hidden_cost_research or sem.ai_fx_break_even_research. An agent can guess the topic but not the precise scope of what is researched or returned.

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 mention of when not to use it, and no routing to alternatives among the many finance-research siblings. The only usage signal is the implicit topic match on 'SWIFT cost', leaving the agent to infer selection criteria on its own.

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