Skip to main content
Glama

frage

Read-onlyIdempotent

Answers a question about vareen.net from the company's own website, with numbered sources, in the language of the question. If the question names two products and a comparison, a side-by-side of the technical data is added. What the website does not say is not answered. For a follow-up in the same conversation pass the id of the previous answer as “nach”.

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

Input Schema

NameRequiredDescriptionDefault
nachNoId of the previous answer (for follow-up questions)
frageYesThe question in natural language

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds real value beyond that: sourced answers with citations, language mirroring, automatic side-by-side comparison for two-product comparisons, and an explicit refusal boundary for unsupported questions. It does not mention any rate limits, error behavior, or how the returned id is surfaced.

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?

Four short sentences, front-loaded with the core action and output shape, then edge behaviors, then the follow-up parameter. Nearly every sentence earns its place; the 'nach' sentence could be folded in but is not wasteful.

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?

With no output schema, the description carries the burden of describing returns and does so well (numbered sources, optional comparison table, language). Combine that with the safety annotations and the tool is nearly fully specified; only error/edge-case behavior beyond the 'not answered' rule 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 already documented, including 'nach' as the previous answer id. The description adds only a small amount — that the id must come from the same conversation — and implies the answer itself carries an id usable as 'nach'. That is marginal value over the schema, so the baseline 3 applies.

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 verb ('answers a question') and a tightly bounded resource ('vareen.net from the company's own website'), and it even specifies the output shape (numbered sources, question's language). It never mentions the sibling tool 'an_vertrieb', so an agent gets no explicit route-selection signal, which keeps this just below a 5.

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?

Usage context is clear: ask questions about the company website, and for a follow-up in the same conversation pass the previous answer id as 'nach'. It also states an exclusion policy — 'What the website does not say is not answered' — which tells the agent what will not be handled. It omits any guidance on when to prefer the sibling an_vertrieb instead.

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