freshservice-mcp

Overview Schema Source Related Servers Discussions Admin

manage_workspace

List or fetch workspace details in Freshservice. Specify the action and workspace ID to retrieve specific workspace information.

Instructions

Manage workspaces.

    Args:
        action: 'list', 'get'
        workspace_id: Required for get

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": {
      "action": "<action>"
    },
    "name": "manage_workspace"
  }
}

Input Schema

Name	Required	Description	Default
`action`	Yes
`workspace_id`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Aug 9, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It reveals the tool is read-only by listing only non-mutating actions, but it does not mention permissions, error handling, or side effects. The absence of explicit safety notes is partially mitigated by the action set.

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 concise and front-loaded with the tool's purpose. The Args section is structured for readability, but 'Manage workspaces' is a generic opener that adds little value. No wasted words, but it could be more direct.

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?

The output schema presumably covers return values, and the description covers parameters and actions. However, it lacks examples, permissions, or edge cases (e.g., behavior when workspace_id is omitted). For a simple read-only tool, it is adequate but leaves some gaps.

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?

The schema lacks descriptions for both parameters (0% coverage), so the description compensates by clarifying valid action values ('list', 'get') and noting that workspace_id is required for get. This adds meaningful semantics beyond the raw 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 clearly identifies the tool as managing workspaces and explicitly lists the supported actions ('list', 'get'), distinguishing it from sibling 'manage_*' tools by resource. It avoids tautology and provides a specific verb-resource pair, though it could be more explicit about the overall purpose.

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?

The description implies usage by listing actions, but it does not specify when to use this tool over alternatives, nor provides exclusions or context. The listing of 'list' and 'get' suggests read-only scenarios, but there is no explicit 'use this when...' guidance.

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