Skip to main content
Glama

Answer a common question

answer_common_question
Read-only

Answer the questions clients ask status403 before booking — what the discovery call covers, how feasibility is assessed, what to prepare, whether delivery is production-ready or prototype, blocked and protected targets, and post-launch support. Also returns how a project runs, from first call to handoff. Pass a query to narrow it to the relevant answers.

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

Input Schema

NameRequiredDescriptionDefault
queryNoOptional keyword, such as "support" or "feasibility". Omit for everything.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

readOnlyHint=true already establishes the safety profile, so the description's incremental contribution is the disclosure that it returns both topic answers and a full project lifecycle ('from first call to handoff'). It says nothing about empty results, matching behavior, or how much content comes back for an unfiltered call, which would matter for a broad retrieval call.

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?

The purpose and the covered topic list are front-loaded, and the query-narrowing tip is placed at the end as an actionable instruction. The middle sentence about project lifecycle slightly duplicates the earlier 'from first call to handoff' framing, but overall there is little waste.

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 read-only, single-optional-parameter FAQ tool with no output schema, the description is complete enough: it tells the agent what subject matter is available and that omitting the query returns everything. Only minor operational details, such as what happens when nothing matches, are absent.

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 the schema already defines the single optional 'query' parameter with an example. The description only echoes that a query narrows results, adding no keyword-matching semantics (exact match vs substring, multiple keywords) beyond the schema.

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 gives a specific verb and resource — answering pre-booking client questions — and enumerates the concrete topics covered (discovery call, feasibility, production-ready vs prototype, blocked/protected targets, post-launch support). It is easy to distinguish from list_services, read_page and search_blog by intent, though it never explicitly contrasts itself with them.

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 context is implied by 'the questions clients ask before booking,' which tells an agent the right situation, and the final sentence explains that a query narrows results. There are no explicit exclusions or named alternatives for when another tool (e.g. search_blog for written content) would be better.

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