Skip to main content
Glama

Search Align's guides

search_guides
Read-only

Find Align's sourced guides on cross-border business payments: SWIFT, SEPA, ACH, Fedwire and UK rails, business accounts for non-resident companies, stablecoins (USDT, USDC, EURC), and rules such as MiCA, the GENIUS Act, the Travel Rule and DAC8. Returns each guide's answer in two sentences and a markdown version to read in full.

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": "search_guides"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many guides to return, 1 to 10 (default 5)
queryYesWhat you want to know, e.g. 'how long does a SEPA transfer take'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered, and the description adds real value by disclosing the return shape: a two-sentence answer per guide plus a full markdown version. It does not discuss ranking, coverage limits, or what happens when no guide matches, which keeps it short of 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.

Conciseness4/5

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

Two sentences, front-loaded with the purpose, then the supported subject matter, then the return format. The topic list is long but earns its space by telling the agent what questions the corpus can answer; nothing is redundant with the name or title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, two-parameter search tool with no output schema, the description covers what the tool does, what topics it can answer, and what the result looks like. An agent has everything needed to call it correctly.

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?

Schema coverage is 100%, so both parameters are documented in the schema and the baseline is 3. The description goes further by scoping what 'query' should contain through the topic enumeration, which meaningfully guides query construction beyond the schema's single example.

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

Purpose5/5

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

States a specific verb and resource ('Find Align's sourced guides on cross-border business payments') and enumerates the concrete topic domains covered (SWIFT, SEPA, ACH, stablecoins, MiCA, DAC8). This is clearly a knowledge-lookup tool, distinguishable from sibling lookup tools like check_iban or stablecoin_rate without opening the schema.

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 implied by the topic enumeration and the 'query' example in the schema, so an agent can infer when this tool fits. However, it gives no explicit when-not guidance and does not route to alternatives (e.g. use check_iban to validate an IBAN, or mica_stablecoin_register for registry data instead of a guide).

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