Skip to main content
Glama

approve_timesheet

Approve a submitted staff time entry for payroll. Call only after the owner approves the specific entry and revision.

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>"
    },
    "name": "approve_timesheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false and openWorld=false, so the safety profile is covered. The description adds value beyond that by disclosing an authorization gate (owner must have approved the specific entry) and by implying revision-scoped, non-idempotent semantics. It does not say what approval does downstream (locks the entry, makes it payable) or what happens if the revision is stale, which keeps it below a 5.

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?

Two short sentences with zero filler; the action and its scope come first and the gating condition follows. Every clause carries information an agent needs before calling.

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 two-parameter mutation with annotations and no output schema, the definition covers purpose and the key precondition, which is the minimum an agent needs. It is not complete: the consequences of approving (entry becomes locked/payable), the behavior on a stale revision, and the fact that the action is not idempotent are left unstated. Those gaps matter for a payroll-affecting write.

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 0%, so the description must carry the param burden, and it only partly does: "the specific entry and revision" loosely maps id to the entry and revision to a version selector. It never explains that revision is an optimistic-concurrency token that must match the current revision or the call fails, nor what id refers to precisely. Some meaning is added, but a caller still has to guess the failure mode.

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?

"Approve a submitted staff time entry for payroll" gives a specific verb (approve) plus resource (staff time entry) and scope (payroll), which separates it from submit_timesheet, return_timesheet and void_timesheet. The only wobble is terminology: the tool is named approve_timesheet but the description speaks of a "staff time entry", leaving a small ambiguity about whether the unit is a timesheet or a line entry.

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?

The second sentence supplies a real precondition: call only after the owner has approved the specific entry and revision. That is clear guidance on when the tool is legitimate to invoke. It stops short of naming alternatives (e.g. return_timesheet or void_timesheet) or stating when not to approve, so it is clear context without exclusions.

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