Skip to main content
Glama
forterro

freshservice-mcp

by forterro

manage_problem_note

List, create, retrieve, update, or delete notes on a Freshservice problem. Use problem ID for all actions; note ID needed for specific operations.

Instructions

Manage notes on a Freshservice problem.

    Args:
        action: One of 'list', 'get', 'create', 'update', 'delete'.
        problem_id: Problem ID (always required).
        note_id: Note ID (required for get/update/delete).
        body: Note body HTML (required for create/update).
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNo
actionYes
note_idNo
problem_idYes

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 must disclose behavioral traits, but it only enumerates parameters and actions. It does not mention side effects like deletion consequences, permissions, or modifications to the problem record, making behavioral expectations unclear.

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

Conciseness5/5

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

The description is compact and well-structured as a docstring with a clear Args list. Every line carries essential information with no redundancy or filler.

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

Completeness4/5

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

Given the presence of an output schema and the straightforward CRUD nature, the description covers the essential parameter semantics and actions. It lacks some context like prerequisites or error handling, but overall is adequate for a tool of this complexity.

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 description adds substantial meaning beyond the schema by listing allowed action values, clarifying required fields per action (note_id for get/update/delete, body HTML for create/update), and specifying problem_id as always required. This compensates fully for the 0% schema coverage.

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 resource as notes on a Freshservice problem. However, it uses the generic verb 'manage' without specifying the exact operations until the Args section, and it lacks explicit differentiation from sibling tools like manage_problem_task.

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 such as manage_problem or manage_problem_task. The description only lists parameters and actions, with no context or exclusions.

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