Skip to main content
Glama
Sign In
fluent-mcp-server

fluent-mcp-server

by jiweiqi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

search_help

Find ANSYS Fluent documentation URLs by entering a search query. Returns relevant manual sections and navigation hints for quick access to help pages.

Instructions

Find ANSYS Fluent documentation URLs for your query.

This tool helps you navigate to the right online documentation. Use WebFetch to retrieve the actual content from the returned URLs.

Args: query: Search term (e.g., "flamelet model", "read case", "turbulence") max_suggestions: Maximum manual section suggestions to return (default: 3)

Returns: URLs and navigation hints for finding the documentation

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

Input Schema

NameRequiredDescriptionDefault
queryYes
max_suggestionsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Describes what the tool returns (URLs and navigation hints) and what is not done (actual content retrieval). No hidden behaviors are implied. Since annotations are absent, the description carries the burden and does well.

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?

Concise, front-loaded description with no unnecessary words. Clear separation of purpose, usage, and parameter details.

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?

Provides enough context for an agent to understand the tool's role, including the need for WebFetch and the nature of the return. Output schema is not shown but mentioned in description; completeness is adequate for a search tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds examples for the 'query' parameter and explains the purpose of 'max_suggestions' with default value. Though schema coverage is 0%, the description compensates by providing practical guidance beyond the schema.

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

Purpose5/5

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

Clearly states it finds ANSYS Fluent documentation URLs. Example queries and the specific parameter descriptions reinforce the purpose. Differentiates from siblings by being a search tool.

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?

Advises using WebFetch to retrieve content from URLs, which is a useful follow-up step. However, it does not explicitly state when to use this tool over siblings like get_manual_link or list_topics.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools