Skip to main content
Glama

list_integration_grants

Read-onlyIdempotent

Lists integration grants where a company is the owner (grants it issued) or the consumer (access it received). Use the as parameter to view what a tenant grants or what it is granted.

Instructions

Grants where this company is the owner (as: "owner", what it gives) or the consumer (as: "consumer", the default — what it receives)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_integration_grants"
  }
}

Input Schema

NameRequiredDescriptionDefault
asNoowner lists grants this tenant issued; consumer lists access granted to this tenantconsumer

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.4

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is fully covered. The description adds the conceptual meaning of the direction flag ('what it gives' vs 'what it receives'), which is useful context beyond the annotations, but it omits pagination, result volume, and any authorization requirements.

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?

One compact sentence with the owner case first and the default second, so the key information is front-loaded and nothing is padded. It is a sentence fragment without a verb and uses 'this company' where the schema says 'tenant', which is a small terminological wrinkle.

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 single-optional-parameter read-only list tool with full annotation coverage and no output schema, the description supplies everything needed to invoke it correctly. Only pagination and result-shape expectations are absent, which is minor at this complexity.

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 100% and the schema already defines owner as 'grants this tenant issued' and consumer as 'access granted to this tenant'. The description restates the same distinction in different words (gives/receives), adding only mild framing value; baseline 3 applies since the schema does the heavy lifting.

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 identifies the resource (integration grants) and splits it into two clearly named facets, owner-issued vs consumer-received. It lacks an explicit verb ('list' is only in the tool name) and never contrasts itself with mutation siblings like grant_integration or revoke_integration_grant, but an agent can still tell what the tool returns.

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?

The description guides the choice between the two enum values and flags consumer as the default, which is genuine selection guidance. It says nothing about when to prefer this tool over the sibling grant/revoke tools or about prerequisites, so guidance is only partial.

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