Skip to main content
Glama

grant_integration

Grant a consumer tenant or agent access to an integration, optionally limiting allowed operations and setting an expiry so permissions apply on the next call.

Instructions

Give a consumer access: integration_id, consumer_tenant_id, optional consumer_agent_id (absent = the whole company), allowed_operations (absent or empty = all operations) and expires_at (ISO 8601). The grant is created active and applies on the consumer's next call

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": {
      "integration_id": "<integration_id>",
      "consumer_tenant_id": "<consumer_tenant_id>"
    },
    "name": "grant_integration"
  }
}

Input Schema

NameRequiredDescriptionDefault
expires_atNoOptional expiry timestamp in ISO 8601 format
integration_idYesAn integration owned by this tenant
consumer_agent_idNoRestrict access to one consumer agent; omit for the entire consumer tenant
allowed_operationsNoAllowed operation names, such as tools or endpoints
consumer_tenant_idYesTenant receiving access

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.4

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare it is a non-read-only, non-destructive, non-idempotent, closed-world write. The description adds real value beyond that: the grant is created 'active' (no separate ratification step), absent allowed_operations means ALL operations, absent agent means the whole company, and it takes effect on the next call. It does not say what happens on a duplicate grant, which matters given idempotentHint=false.

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 dense sentence with parameter names front-loaded in backticks and defaults attached inline; no filler. The heavy use of parentheticals makes it slightly harder to scan, but nothing is wasted.

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 5-parameter mutation with no output schema and minimal annotations, the description covers scoping, defaults, activation state, and timing. The main gap is the return value (e.g., whether a grant ID comes back), which no output schema documents either.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds decisive semantics the schema lacks: empty allowed_operations grants every operation (a significant default), and absent consumer_agent_id scopes to the whole tenant. It does not clarify format expectations for allowed_operations values beyond the schema's example.

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+resource: 'Give a consumer access' to an integration, and enumerates the grant's dimensions (tenant, optional agent, allowed operations, expiry). An agent can distinguish this from revoke/ratify siblings by the word 'give ... access', though no sibling is named explicitly.

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?

No when-to-use or when-not guidance: nothing says whether to use this versus ratify_integration_grant, whether a credential must exist first, or what happens if a grant already exists. The only usage-adjacent statement is that the grant 'applies on the consumer's next call', which is propagation behavior, not selection guidance.

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