Schema | FS_MCP_thin

FS_MCP_thin

Describes the environment variables required to run the server.

Name	Required	Description	Default
`FRESHSERVICE_DOMAIN`	Yes	Your Freshservice URL host, e.g. acme.freshservice.com
`FRESHSERVICE_API_KEY`	Yes	Your personal API key from Freshservice Profile Settings

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Features and capabilities supported by this server

Protocol revision2025-11-25

Functions exposed to the LLM to take actions

Name	Description
search_ticketsA	Search Freshservice tickets using filter query syntax. Examples: "status:2" for open, "priority:4" for urgent, "status:2 AND priority:4" for open+urgent.
list_open_ticketsB	List open tickets (status:2)
get_ticketA	Retrieve full details for a specific Freshservice ticket by ID
get_ticket_conversationsA	Retrieve all conversations (replies and notes) for a ticket
get_ticket_notesA	Retrieve only private/internal notes for a ticket
get_service_request_itemsB	Retrieve requested items for a service request ticket
search_kbB	Search for solution articles by keyword
get_kb_articleB	Retrieve full content of a solution article
list_problemsB	List recent Problem records
get_problemA	Retrieve full details of a specific Problem record
list_assetsC	List assets in inventory
get_assetB	Retrieve full details of a specific asset
list_softwareC	List software inventory
search_requestersA	Find requesters by name or email
get_requesterA	Retrieve full details of a specific requester by ID
search_agentsC	Find agents by email
get_agentA	Retrieve full details of a specific agent by ID
get_agent_groupA	Retrieve full details of a specific agent group/team by ID
get_requester_ticketsA	Retrieve all tickets for a specific requester (user ticket history)
get_requester_assetsA	Retrieve all assets assigned to a specific requester
list_canned_responsesC	List canned response templates
list_service_catalog_itemsA	List items in the service catalog
get_service_catalog_itemB	Retrieve details of a specific service catalog item

Interactive templates invoked by user choice

Name	Description
`triage_ticket`	Standard workflow for assessing and responding to a new ticket
`summarize_ticket`	Generate a concise summary of a ticket for handoff or escalation
`draft_reply`	Draft a professional response to a customer based on ticket context
`sla_check`	Analyze if a ticket is at risk of breaching SLA

Contextual data attached and managed by the client

Name	Description
`ticket-fields`	All ticket fields including custom fields and valid values
`agent-groups`	List of all agent groups (support teams)
`sla-policies`	All configured SLA policies with response/resolution targets
`business-hours`	Configured working hours schedules
`requester-fields`	Custom field schema for requesters/users
`departments`	Organizational departments

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

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cbreland-DLR/FS_MCP_thin'

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