Skip to main content
Glama

ratify_integration_grant

Confirms a provisional integration grant by moving it from pending_ratification to active, including grants registered by migrations; repeated calls on active grants return them unchanged.

Instructions

Confirm a provisional grant (pending_ratification → active), e.g. one registered by a migration. Repeating it on an active grant returns the grant unchanged

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": {
      "grant_id": "<grant_id>"
    },
    "name": "ratify_integration_grant"
  }
}

Input Schema

NameRequiredDescriptionDefault
grant_idYesGrant to ratify

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.4

TDQS

A3.8/5.0
Behavior3/5

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

The description adds real behavioral detail beyond the annotations: the precise state transition, and the fact that a repeat call on an active grant returns it unchanged rather than erroring. However, that retry statement reads as idempotent behavior while the annotations declare idempotentHint=false, creating ambiguity rather than resolving it. It also says nothing about failure modes (unknown grant_id, grant in a revoked state).

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 clauses, front-loaded with the action and state transition, followed by the edge-case behavior. Every sentence earns its place and there is no filler.

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

Completeness4/5

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

For a one-parameter state-transition tool with no output schema, the description covers what changes, when to call it, and the already-active case, which is what an agent needs to invoke it safely. Missing are the error/precondition behavior for non-provisional or unknown grants and any mention of the complementary tool that grants integration in the first place.

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 coverage is 100% and the single grant_id parameter is already documented as a UUID with 'Grant to ratify'. The description contributes only the context that the grant must be provisional, which the schema itself does not encode, so it is additive but minimal — baseline 3 applies.

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 and resource plus the exact state transition it performs ('pending_ratification' → 'active'), which is far more informative than the bare name. It does not explicitly distinguish itself from the sibling grant_integration (the tool that presumably creates the provisional grant), so the agent must infer that boundary from the state names alone.

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 concrete triggering case ('one registered by a migration') and describes what happens when the precondition no longer holds (already active). It stops short of naming the sibling that produces provisional grants or of excluding other states such as revoked grants, so the routing guidance is clear but not explicit.

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

Deploy Server

Other Tools