Skip to main content
Glama

About Advisorn

about_advisorn
Read-onlyIdempotent

Facts about Advisorn GmbH: what it does, for whom, where, languages, managing partner, contact and main pages. Use when the user asks who Advisorn is or whether it can help.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "about_advisorn"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer: en, it, de or fr.en

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds genuine value beyond that by disclosing the content scope of the answer (company profile, location, languages, managing partner, contact, main pages), which tells the agent what it will actually get back. It says nothing about answer length, formatting or whether the response is a fixed snapshot, so it is not fully exhaustive.

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, both load-bearing: the first lists the content covered, the second states when to invoke it. The purpose comes first and the usage cue second, with no filler or restatement of the tool name.

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

Completeness4/5

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

For a simple, zero-required-parameter, read-only lookup with no output schema, the definition supplies purpose, content scope and trigger condition — enough to call it correctly. The only omission is that output language is controlled by the lang parameter, which the schema already documents.

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?

There is a single optional parameter with 100% schema description coverage, including an enum of en/it/de/fr and a default, so the schema already carries the semantics. The description never mentions the language parameter or that the answer's language is user-selectable, so it adds nothing on this dimension. Baseline 3 applies when the schema does the work.

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

Purpose4/5

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

The description names a specific resource (facts about Advisorn GmbH) and enumerates exactly what those facts cover: what it does, for whom, where, languages, managing partner, contact and main pages. That is far more concrete than a generic 'get info' statement, and the usage clause ('who Advisorn is or whether it can help') implicitly separates it from generic siblings like search or get_answer, though it never names an alternative.

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?

It gives an explicit trigger: use when the user asks who Advisorn is or whether it can help. That is a clear use context with no ambiguity about the intent it serves. It stops short of a 5 because it offers no exclusion ('do not use for X, use Y instead') and does not name any sibling tool to route to.

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