Skip to main content
Glama

Company invitations

company_invitations_list
Read-onlyIdempotent

Invitations sent for one of your companies (owners and admins only): masked e-mail, role, status, expiry and how often it was sent. The invitation link itself is not shown. Pass nextCursor to get the next page.

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": {
      "company": "<company>"
    },
    "name": "company_invitations_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many rows (1-50).
cursorNonextCursor from the previous page.
statusNoDefault: all statuses.
companyYesCompany ref (CO-XXXXXXXX) from company_list_mine.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: results are permission-gated to owners/admins, e-mail addresses are masked, and the invitation link is deliberately withheld — all things an agent could not infer from annotations.

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?

Three short sentences, front-loaded with what is returned and the permission gate, then pagination. The cursor sentence is mildly redundant with the schema but not wasteful enough to hurt readability.

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?

With no output schema, the description compensates by listing the returned fields and explicitly noting the omitted invitation link, which is important for an agent reasoning about available data. Combined with full schema coverage and annotations, only minor gaps (e.g., default ordering) remain.

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%, so all four parameters (limit, cursor, status, company) are already documented, including the enum and the CO-XXXXXXXX pattern. The description's only parameter note, 'Pass nextCursor to get the next page', largely restates the cursor field's schema description, so it adds little beyond the baseline.

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 names the resource (invitations for a company) and enumerates the returned fields (masked e-mail, role, status, expiry, send count), so an agent knows exactly what this returns. It does not explicitly contrast with siblings like company_invite_create or company_invite_resend, but the read-only listing nature 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 states a real usage constraint — owners and admins only — and explains pagination via nextCursor. However, it never says when to prefer this over related tools (e.g., company_members_list) or what happens for non-admin callers, leaving selection guidance implied.

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