Skip to main content
Glama

reject_cosigner_action

Reject a pending action as co-signer.

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

Input Schema

NameRequiredDescriptionDefault
reasonNoOptional rejection reason
pendingApprovalIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure and largely drops it. It does not say whether rejection is irreversible, whether the optional reason is shown to the requester, what permissions or co-signer role is required, or what state the pending action moves to afterwards.

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?

A single front-loaded sentence with no wasted words and the verb leading. It is efficient, though the brevity reflects under-specification rather than disciplined compression.

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 destructive mutation with no annotations and no output schema, the definition should explain preconditions, sourcing of the approval ID, and consequences of rejection. Instead it supplies one sentence, leaving the agent's main open questions unanswered.

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 coverage is only 50%: 'reason' is documented in the schema, but 'pendingApprovalId' has no description anywhere. The description adds no meaning about where that ID comes from (presumably list_pending_cosigner_approvals) or the effect of supplying vs. omitting a reason.

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 ('Reject') and resource ('a pending action') plus the actor role ('as co-signer'), which is clear enough for an agent to know what will happen. It does not distinguish itself from the obvious sibling approve_cosigner_action or relate to list_pending_cosigner_approvals, so it falls short of the top tier.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no mention of the alternative tool (approve_cosigner_action). The only signal is the word 'pending' in the name/description, leaving the agent to infer both the precondition and the routing decision.

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