Skip to main content
Glama
forterro

freshservice-mcp

by forterro

manage_problem_time_entry

List, retrieve, create, update, or delete time entries for a Freshservice problem. Capture agent, time spent, note, and billable status to track work effort on problem resolution.

Instructions

Manage time entries on a Freshservice problem.

    Args:
        action: One of 'list', 'get', 'create', 'update', 'delete'.
        problem_id: Problem ID (always required).
        time_entry_id: Time entry ID (required for get/update/delete).
        agent_id: Agent who performed the work.
        note: Description of work performed.
        time_spent: Time in "hh:mm" format (required for create).
        executed_at: ISO datetime when work was performed.
        task_id: Associated task ID.
        billable: Whether the time is billable.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
actionYes
task_idNo
agent_idNo
billableNo
problem_idYes
time_spentNo
executed_atNo
time_entry_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description must disclose safety/mutation characteristics. It does explain action-specific required parameters and formats, but it does not state whether delete is permanent, permission requirements, rate limits, or any side effects; this leaves important behavioral ambiguity for a mutating CRUD tool.

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 a compact docstring: a one-line purpose followed by a flat argument list. Each line adds a unique semantic: allowed action values, required IDs per operation, formats, and associations. No 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?

For a 9-parameter CRUD tool with no annotations but an output schema, the description covers all input parameters and per-action dependencies; it lacks explicit examples or error/edge-case guidance, but the provided action/field matrix is sufficient for correct invocation.

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?

With 0% schema description coverage, the description compensates fully by defining all nine parameters, including value domains (action choices), formatting ('hh:mm', ISO datetime), and action-specific requirements. This is essential semantics beyond the schema's bare names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Manage') with a clear resource ('time entries on a Freshservice problem') and enumerates supported actions, making its scope distinct from sibling tools like manage_change_time_entry or manage_problem_note.

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?

It implies usage for problem time-entry CRUD operations and defines when each action requires additional arguments (e.g., time_entry_id for get/update/delete, time_spent for create), but it never explicitly contrasts with sibling time-entry tools or states when not to use it.

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