Skip to main content
Glama
forterro

freshservice-mcp

by forterro

manage_asset

Create, update, delete, restore, list, search, and move assets in Freshservice with a single tool.

Instructions

Unified asset operations.

    Args:
        action: One of 'create', 'update', 'delete', 'delete_permanently',
                'restore', 'get', 'list', 'search', 'filter', 'move',
                'get_types', 'get_type'
        display_id: Asset display ID (get, update, delete, restore, move, details)
        asset_type_id: Asset type ID (create — MANDATORY, get_type)
        name: Asset name (create — MANDATORY)
        asset_tag: Asset tag (e.g. 'ASSET-9')
        impact: 'low', 'medium', or 'high' (default: 'low')
        usage_type: 'permanent' or 'loaner' (default: 'permanent')
        description: Asset description
        user_id: User ID (Used By)
        location_id: Location ID
        department_id: Department ID
        agent_id: Agent ID (Managed By)
        group_id: Group ID (Managed By Group)
        assigned_on: ISO date when assigned
        workspace_id: Workspace ID (create, list, move)
        type_fields: Asset-type-specific fields dict
        asset_fields: Generic update fields dict (update — alternative to explicit params)
        search_query: Search by name/tag/serial (search)
        filter_query: Filter expression (filter)
        include: Include extra data, e.g. 'type_fields' (list, get)
        order_by: Sort field (list)
        order_type: 'asc' or 'desc' (list)
        trashed: Include trashed assets (list, search)
        page: Page number
        per_page: Items per page
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
pageNo
actionYes
impactNo
includeNo
trashedNo
user_idNo
agent_idNo
group_idNo
order_byNo
per_pageNo
asset_tagNo
display_idNo
order_typeNo
usage_typeNo
assigned_onNo
descriptionNo
location_idNo
type_fieldsNo
asset_fieldsNo
filter_queryNo
search_queryNo
workspace_idNo
asset_type_idNo
department_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

With no annotations, the description carries the full disclosure burden. It does reveal that delete and delete_permanently are distinct actions (implying soft vs hard delete) and that restore exists, but it fails to clarify permissions, side effects, error behavior, or what responses look like. Given the tool's complexity and destructive potential, this is a significant transparency gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The parameter list is long but each line carries useful scoping information. The opening phrase 'Unified asset operations' is too vague, and the structure fails to group params by action or provide a quick reference. It is not conciseness but rather an unstructured dump that could be better organized.

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?

For a tool with 25 parameters and 11 actions, this description is under-specified. It lacks an action-by-action requirements matrix, no examples of valid payloads, no explanation of how search vs filter vs list differ, and no mention of pagination or output behavior. While an output schema exists, the description still leaves too much ambiguity for an agent to invoke the tool correctly.

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 0%, so the description must compensate. It does add meaning by stating required params for create, including examples (e.g., 'ASSET-9'), and indicating which actions each param applies to. However, some parameters (e.g., filter_query, order_by, type_fields) receive only minimal or no semantic explanation, leaving the agent with partial understanding.

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 this is a unified asset operations tool with an explicit action enum covering CRUD, search, list, move, and type operations. However, it does not differentiate from sibling tools like manage_asset_details or manage_asset_relationship, so the line between core asset management and these auxiliary tools is unclear.

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?

There is no guidance on when to use this tool versus alternatives. The only usage hints are per-parameter parentheticals like 'create — MANDATORY', but there is no consolidated action matrix or explicit mention of sibling tools. For a dispatcher with 11 actions, the agent is left to infer parameter-action mappings from scattered comments.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/forterro/freshservice_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server