Skip to main content
Glama

Link to contact Advisorn

start_request
Read-onlyIdempotent

When the user wants Advisorn's help with their own case, returns the link that opens the right request form on advisorn.com (about one minute, the person fills it in; a non-disclosure agreement can be requested there). Sends nothing and stores nothing. Areas: sof (source of funds report), inv (stolen crypto, tracing, freezes), expert (expert report for proceedings), regulation, data, other.

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": {
      "area": "<area>"
    },
    "name": "start_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaYesThe kind of help needed.
langNoLanguage of the answer: en, it, de or fr.en

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Adds real behavioral context beyond the annotations: "Sends nothing and stores nothing," the human-side handoff ("about one minute, the person fills it in"), and that an NDA can be requested there. This complements rather than repeats the readOnly/idempotent hints; only the response shape (a bare URL) is left implicit.

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?

Front-loads the condition and the action before the supporting detail, and every clause carries information an agent needs. The trailing area list is dense but necessary for routing a correct area value.

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 link-returning tool with two enum parameters and full annotation coverage, nothing material is missing: the trigger, the side-effect profile, the human follow-up, and the option semantics are all present.

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 the baseline is 3, but the description expands every area token with meaning the schema lacks: sof = source of funds report, inv = stolen crypto, tracing, freezes, expert = expert report for proceedings. The lang parameter is left to the schema, which already documents it fully.

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: "returns the link that opens the right request form on advisorn.com." It also frames the trigger (the user wants Advisorn's help with their own case), which cleanly separates it from get_answer, search, or list_topics.

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

Usage Guidelines4/5

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

Gives an explicit activation condition: only when the user wants help with their own case. No exclusions or named alternative tools are offered, but sibling tools here serve different ends, so the gap is minor.

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