Skip to main content
Glama

Get a time entry

get_time_entry
Read-onlyIdempotent

One time entry by id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_time_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe id of the entry

Output Schema

NameRequiredDescriptionDefault
idYes
costNo
hoursYesDecimal hours, such as `1.50`
notesNo
stateYes
amountNo
task_idNo
billableNo
currencyNo
spent_onYes
client_idYes
cost_rateNo
member_idYes
task_nameNo
invoice_idNo
project_idYes
updated_atNo
client_nameNo
hourly_rateNo
inserted_atNo
member_nameNo
project_nameNo
cost_currencyNo
invoice_numberNo
project_task_idYes
billed_elsewhere_onNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The description adds only the word "one" (single-entity return); it says nothing about behavior for a missing/invalid id, error semantics, or scope constraints. With annotations carrying the load, this is thin additional value.

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?

It is four words with zero padding, and the key information (single entry, keyed by id) is front-loaded. It loses a point for being a fragment rather than a complete, self-contained statement of the operation.

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?

For a trivial one-parameter read tool with full schema coverage and an output schema, the essentials are covered. Still, it omits what happens when the id does not resolve, which is the main failure mode an agent would want to know about.

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 description coverage is 100% and the sole parameter is typed as a UUID, so the schema already does the work. The description's "by `id`" merely restates the parameter name and adds no format or sourcing detail beyond it; baseline 3 applies.

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

Purpose3/5

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

"One time entry by `id`" identifies the resource (time entry) and the retrieval key (id), and the singular "one" implicitly contrasts with list_time_entries. However, it is a sentence fragment with no verb, so the agent must infer that this is a read/fetch operation rather than, say, a lookup that returns a summary.

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 instead of list_time_entries or another get_* tool, and no mention of prerequisites such as needing a valid, existing entry id. The single-key fetch is inferable only from the schema, not stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources