Skip to main content
Glama

void_timesheet

Destructive

Void a draft or submitted staff time entry after owner approval.

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": "void_timesheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
reasonYes
revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered elsewhere. The description adds value on top of that by naming what gets affected (a draft or submitted time entry) and the approval gate, though it says nothing about irreversibility or what happens if the revision token is stale.

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 short sentence with the action and the eligibility conditions front-loaded; nothing is wasted. The trailing 'after owner approval' clause is slightly ambiguous in attachment but not wasteful.

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 destructive, non-idempotent mutation with three undocumented parameters and no output schema, the description covers the verb and preconditions but omits parameter meaning and failure/reversibility behavior. It is minimally adequate rather than complete.

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?

All three required parameters have zero schema description coverage, so the description carries the full burden and explains none of them. In particular 'revision' (an optimistic-concurrency token) and the required 'reason' are unexplained, which is a serious gap for a destructive operation.

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?

States a specific verb ('Void') and resource ('staff time entry') and narrows scope to entries in 'draft or submitted' state. It does not name or distinguish itself from adjacent siblings such as return_timesheet or approve_timesheet, so an agent must infer the routing from its own knowledge.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a real precondition ('after owner approval') and eligible state constraint ('draft or submitted'), which are the key conditions for calling it. It stops short of explicitly excluding alternatives or naming a sibling when the entry is in another state.

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