Skip to main content
Glama

Goodeye

by dev.goodeye
OverviewDiscussionsAdmin

list_invitations

Read-only

List invitations visible to the caller.

filter="received" returns invitations where you are the recipient. filter="sent" returns invitations you created. filter="all" combines both. state="pending" excludes expired and resolved rows. Cursor-paginated. Returns {items: [...], next_cursor: str | null}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of items to return in one page (1 to 200).
stateNoWhich states to include: 'pending' only, or 'all' (includes expired and resolved invitations).pending
cursorNoPagination cursor from a previous response's next_cursor; omit to start from the first page.
filterNoWhich invitations to return: 'received' (addressed to you), 'sent' (you created), or 'all'.received

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / filter / description
      Previous value: -"'received' | 'sent' | 'all'"New value: +"Which invitations to return: 'received' (addressed to you), 'sent' (you created), or 'all'."
    • changedInput schema / properties / state / description
      Previous value: -"'pending' | 'all'"New value: +"Which states to include: 'pending' only, or 'all' (includes expired and resolved invitations)."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds transparency by explaining cursor pagination, return format, and the effect of filter and state parameters.

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?

The description is concise and well-structured: first sentence states purpose, then parameter explanations with examples, then pagination and return format. No wasted words.

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

Completeness5/5

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

Given the parameter count, schema richness, and presence of output schema, the description fully covers behavior: listing with filters, state, and cursor pagination. No gaps.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds significant value by providing examples and clarifying parameter behavior (e.g., 'filter="received" returns invitations where you are the recipient').

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'List invitations visible to the caller' and elaborates on filters and pagination, distinguishing it from siblings like accept_invitation or cancel_invitation.

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 implies usage for viewing invitations with various filters, but does not explicitly state when to use this tool versus alternatives or provide exclusion criteria.

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

All Goodeye toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources