Freshdesk MCP Server

Overview Schema Source Related Servers Discussions Admin

get_solution_article

Retrieve the full content of a knowledge base article by providing its article ID to access solutions and troubleshooting information.

Instructions

Retrieve the content of a specific knowledge base article.

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

Input Schema

Name	Required	Description	Default
`article_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 15, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are present, so the description must fully convey behavior. It only states 'retrieve', implying read-only, but does not disclose any permissions, rate limits, or side effects. The output schema exists but is not described, leaving ambiguity about what 'content' includes.

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 superfluous words, achieving maximum conciseness. However, it could benefit from a bit more structure, such as specifying what 'content' entails or the expected output.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity of the tool (one parameter, output schema exists), the description covers the basic purpose. But it fails to provide enough context for an AI agent to understand potential limitations, error cases, or whether the article content includes metadata. Acceptable but not thorough.

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

Parameters2/5

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

The schema has 0% documentation coverage for parameters. The description mentions 'specific knowledge base article' but does not explain the 'article_id' parameter's format, source, or constraints. The parameter is required but lacks semantic explanation beyond its name.

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 clearly states the action ('Retrieve') and the resource ('content of a specific knowledge base article'), with an implication that the article ID is the key. It distinguishes from sibling 'search_solution_articles' which is a search tool. However, it does not articulate the scope or any unique aspects beyond the basic retrieval.

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 alternatives, nor are there any usage conditions or prerequisites mentioned. The description lacks context for when retrieval is appropriate compared to searching or other actions.

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