Skip to main content
Glama

Search Advisorn's answers

search
Read-onlyIdempotent

Use first for any question on crypto source of funds, stolen or frozen crypto, blockchain evidence and expert reports, crypto tax, crypto regulation (MiCA, Travel Rule, FINMA, SRO, CARF, DAC8) or data protection in Switzerland. Searches Advisorn's questions and answers, glossary and insights in English, Italian, German or French and returns the best matches with a one-line summary and the page link. Then call get_answer (type question) or get_term (type term) for the full text.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer: en, it, de or fr.en
queryYesThe user's question or keywords, in any of the four languages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely useful behavior beyond that: results are ranked best matches, each carrying a one-line summary and page link (snippet only, not full text), and there is no output schema to convey this otherwise. It says nothing about result count, ranking or empty-result behavior, keeping it mid-range rather than rich.

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

Conciseness5/5

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

Two sentences with zero filler: the trigger condition and topic scope come first, the return shape second, and the next-step routing last. The parenthetical regulation list is dense but each item earns its place by anchoring retrieval on acronym queries.

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?

With no output schema, the description still tells the agent what comes back (best matches, one-line summary, page link) and how to continue to full text, which is what the agent needs to decide and act. Nothing material for correct invocation is missing.

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% and both parameters are documented there, including the language enum, so baseline is 3. The description adds only the cross-lingual hint that the query may be in any of the four languages, which largely restates the schema.

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 ('Searches Advisorn's questions and answers, glossary and insights') and enumerates the subject domains and languages covered, so an agent can tell exactly what corpus is being searched. It also names get_answer and get_term as the follow-up tools, distinguishing this retrieval step from full-text retrieval.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit entry-point rule ('Use first for any question on...') with a concrete topic list, plus an explicit sequencing instruction: call search first, then get_answer (type question) or get_term (type term). Both the when and the alternatives are spelled out.

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