Skip to main content
Glama

request_approval

Submits an invoice to the finance manager for approval and returns the approval decision the next day.

Instructions

Send an invoice to the finance manager for approval. The decision arrives the next day.

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": {
      "invoice_id": "<invoice_id>"
    },
    "name": "request_approval"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
invoice_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the decision is asynchronous and arrives the next day, but it does not explain side effects such as whether the invoice is locked, what happens on rejection, or whether the note is forwarded to the approver.

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 no wasted wording, and the core action is front-loaded before the timing detail. The brevity is effective even though more behavioral detail would be useful elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is an action-oriented approval workflow tool with no annotations, no output schema, and no parameter descriptions. The description gives useful timing context but omits important operational details such as permissions, result behavior, and parameter meaning.

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%, so the description must compensate for both parameters. It does not explain the expected format of invoice_id or what the optional note is used for, leaving the schema to carry undocumented parameters.

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 states a specific verb and resource: sending an invoice to the finance manager for approval. It is clear enough to distinguish this from payment or rejection actions, though it does not explicitly name or contrast sibling tools.

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?

Usage is implied by the phrase 'for approval' and the next-day decision timing, which suggests this is the submission step before an approval outcome. However, there is no explicit guidance on when to choose this over related tools such as send_email, pay_invoice, or reject_invoice, and no prerequisites are stated.

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