Skip to main content
Glama

Ask Envoyant

ask_question
Read-only

Answers questions about Envoyant with answers Envoyant approved. Returns a text approved by Envoyant, unchanged; nothing is generated. Do not include personal details.

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

Input Schema

NameRequiredDescriptionDefault
answerIdNoOptional. The answerId (a UUID) of one of the suggestedQuestions of an earlier result, to get that answer.
languageNoOptional. BCP 47 language of the question, e.g. "en" or "nl".
questionYesThe question, in plain language.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered. The description adds genuinely useful behavior: responses are pre-approved canned text returned unchanged and nothing is generated, which changes how an agent should interpret and present the result, plus a privacy constraint on input.

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?

Three short sentences, front-loaded with the core purpose, and each contributes (purpose, output nature, input restriction). The phrase 'with answers Envoyant approved' is slightly redundant with the following 'approved by Envoyant', but nothing is wasted overall.

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 an output schema present, return values need not be detailed, and the description still clarifies that the returned text is approved and unmodified. For a read-only Q&A tool with a well-described three-parameter schema, this is essentially complete; only routing guidance versus siblings 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%, including an explanation of answerId as a reference to a suggestedQuestions UUID, so the schema carries parameter meaning. The description only adds the 'no personal details' constraint on the question text, which is a modest addition.

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?

States a specific verb and resource: it answers questions about Envoyant. An agent can tell what it does without opening the schema, and the scope (Envoyant Q&A) is narrow enough to distinguish it from get_business_info and request_quote, though no sibling is named explicitly.

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 only implied: it is for asking questions about Envoyant. Nothing tells the agent when to prefer this over get_business_info or request_quote, nor when to pass answerId instead of question, and no prerequisites or exclusions are stated beyond the privacy warning.

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