Ask FusionAuth question
ask_fusionauth_questionAsk technical questions about FusionAuth.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | The question about FusionAuth to ask |
mcp-docs
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
C2.7/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It does not disclose what happens when a question is asked, whether it returns an answer, any limitations, or whether it is a read-only operation. The single sentence provides no behavioral context.
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 description is a single sentence with no filler, making it very concise and front-loaded. However, it is also under-specified, which slightly reduces its effectiveness, but it does earn its place by stating the primary function.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity, the description does communicate the basic purpose, but it lacks usage guidance, expected output, and any behavioral caveats. The presence of a sibling tool without differentiation guidance makes it incomplete.
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 covers the single parameter fully with description. The tool description adds 'technical' as a qualifier, providing slight additional meaning about the type of question. Baseline 3 is appropriate since schema does most of 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 uses a clear verb ('ask') and specific resource ('technical questions about FusionAuth'), distinguishing it from the sibling search_fusionauth_sources which searches sources. However, it doesn't specify the scope or expected behavior beyond asking questions.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus search_fusionauth_sources, nor any mention of alternatives or exclusions. The description only states a general function.
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.
TDQS
B3/5.0
Disambiguation5/5
The two tools have clearly distinct purposes: 'ask_fusionauth_question' is for direct Q&A about FusionAuth, while 'search_fusionauth_sources' is for searching documentation. There is no overlap or ambiguity between these functions, making tool selection straightforward for an agent.
Naming Consistency5/5
Both tool names follow a consistent verb_noun pattern with clear action descriptors ('ask' and 'search') and a common domain identifier ('fusionauth'). The naming is predictable and readable, with no deviations in style or convention.
Tool Count2/5
With only 2 tools, the server feels under-scoped for a documentation assistant. While the tools cover basic Q&A and search, the domain of FusionAuth documentation likely requires more operations (e.g., browse, summarize, or filter content) to be effective, making the toolset thin and potentially limiting for agents.
Completeness2/5
The toolset is severely incomplete for a documentation server. It lacks essential operations such as retrieving specific documentation pages, listing available resources, or handling updates. Agents will face dead ends when trying to perform common documentation tasks beyond simple questions and searches.