Skip to main content
Glama
forterro

freshservice-mcp

by forterro

manage_location

List, retrieve, create, update, delete, or filter Freshservice locations with address and contact details to keep your service desk organized.

Instructions

Manage Freshservice locations.

    Args:
        action: One of 'list', 'get', 'create', 'update', 'delete', 'filter'.
        location_id: Location ID (required for get/update/delete).
        name: Location name (required for create).
        line1/line2/city/state/country/zipcode: Address fields.
        contact_name: Contact person name.
        email: Contact email.
        phone: Contact phone.
        parent_location_id: Parent location ID for hierarchical locations.
        query: Filter query for 'filter' action (e.g. "name:'New York'").
        page/per_page: Pagination.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNo
nameNo
pageNo
emailNo
line1No
line2No
phoneNo
queryNo
stateNo
actionYes
countryNo
zipcodeNo
per_pageNo
location_idNo
contact_nameNo
parent_location_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 burden of behavioral disclosure. It lists actions like delete and create but does not warn about destructive side effects, permission requirements, or whether operations are reversible. The lack of behavioral context is a significant gap for a mutation-capable tool.

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 structured docstring listing parameters with concise explanations. It is appropriately sized for a 16-parameter tool, with a clear front-loaded purpose statement followed by a logically grouped Args list. Slightly verbose but each line earns its place.

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 tool is complex with multiple actions and 16 parameters, and the description covers the basic action-parameter mapping well. However, it lacks details on error handling, permissions, output behavior beyond what the output schema provides, and nuanced usage scenarios. Given the output schema exists, return values are covered, but behavioral expectations and limitations are under-explained.

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

Parameters5/5

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

The schema has 0% description coverage, but the description compensates excellently by explaining each parameter's role, including which actions require which parameters (e.g., 'location_id required for get/update/delete', 'query for filter'). It also clarifies grouping of address fields and hierarchical location semantics, adding meaning far beyond the bare 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 states 'Manage Freshservice locations' and immediately enumerates the supported actions (list, get, create, update, delete, filter), making the tool's purpose clear. However, it does not explicitly distinguish itself from sibling tools, though the name 'manage_location' already differentiates it by resource.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., manage_department, manage_asset). It lists actions but does not mention context, prerequisites, or alternatives. The only implicit guidance is the resource name, but the description fails to explicitly say 'use this for location operations'.

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