Skip to main content
Glama

return_timesheet

Return a submitted or approved staff time entry to draft for correction.

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>",
      "revision": "<revision>",
      "reason": "<reason>"
    },
    "name": "return_timesheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
reasonYes
revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, and the description is consistent with a state-changing, repeat-sensitive operation. Beyond that it adds little: it does not say whether the staff member is notified, whether the change is reversible, whether prior approvals are invalidated, or what happens on a stale revision, all of which matter for a workflow mutation.

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?

One front-loaded sentence with no filler, and the key scope constraint appears before the purpose clause. It is efficient but so terse that the brevity becomes under-specification rather than clarity.

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 three-parameter mutation with no output schema and no description coverage on any parameter, the definition is thinner than the complexity warrants. The state transition is clear, but the agent still lacks the semantics of revision and reason and any sense of side effects or failure modes.

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

Parameters2/5

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

Schema description coverage is 0% for three required parameters (id, revision, reason), so the description carries the full burden and adds no meaning at all. Most importantly it never explains that 'revision' is presumably a concurrency/version token or that 'reason' is recorded and required, both of which materially affect correct invocation.

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 gives a specific verb and resource ('Return a ... staff time entry') plus the state transition target ('to draft') and the eligible source states ('submitted or approved'), which cleanly separates it from submit_timesheet, approve_timesheet and void_timesheet. It stops short of naming any sibling explicitly, so differentiation is inferable rather than stated.

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?

'for correction' hints at the intent, and the source-state restriction (only submitted or approved entries) implicitly tells the agent when the call is valid. However, there is no explicit when-not guidance, no mention of prerequisites such as permissions or the entry being locked, and no named alternative for other state changes.

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