Skip to main content
Glama

approve_cosigner_action

Approve a pending action as co-signer. Use with list_pending_cosigner_approvals.

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": {
      "pendingApprovalId": "<pendingApprovalId>"
    },
    "name": "approve_cosigner_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
pendingApprovalIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a consequential mutation but says nothing about whether approval is irreversible, whether it requires being a registered co-signer, whether multiple approvals are needed to reach a threshold, or what happens to the underlying action on success.

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?

Two short sentences with no filler and the core action front-loaded. Nothing is wasted, though the second sentence is more of a pointer than substantive detail.

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?

For a mutation tool with no annotations and no output schema, the description should clarify permissions, side effects, and the post-approval state. It leaves the agent guessing about what changed and what to do or report next.

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% for the single required parameter, so the schema adds no meaning beyond the name 'pendingApprovalId'. The description's reference to list_pending_cosigner_approvals implicitly tells the agent where to obtain that ID, which is useful but thin compensation.

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 uses a specific verb and resource ('approve a pending action') and scopes it by role ('as co-signer'), which distinguishes it from action-proposal siblings. It does not explicitly contrast with reject_cosigner_action, but the operation is unambiguous.

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?

It gives one concrete usage pointer by naming list_pending_cosigner_approvals as the companion tool, implying the workflow of discover-then-approve. It stops short of stating when not to use it or pointing to reject_cosigner_action as the alternative outcome.

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