Skip to main content
Glama
Sign In

Ankra

by ai.ankra
OverviewDiscussionsAdmin

List project members

list_project_members
Read-only

Who reaches one project (the twin of ankra project members): each member's user_id, email, role and how they reach it - via organisation (their organisation role reaches every project) or via project (an assignment scoped to this project) - plus the project-only invitations naming it that are still pending or expired. project_id comes from list_projects; a project the caller cannot reach answers not found. Needs projects.read. Read-only.

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": {
      "project_id": "<project_id>"
    },
    "name": "list_project_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesUUID of the project (from list_projects).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/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 is consistent ('Read-only'). Beyond that it adds real behavioral context: the required permission scope, the not-found behavior on unreachable projects, and the fact that expired invitations are included — none of which is in the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose and free of filler, but the single sentence is heavily nested with parentheticals and em-dashes, making the return-shape portion harder to parse than it needs to be.

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 carries the return-value burden and does so by enumerating members, their access path, and pending/expired invitations. Only pagination or result-size behavior is missing, which is minor for a single-project listing.

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 parameter already documents itself as a project UUID from list_projects, so the description only echoes that. Baseline 3 applies since the schema carries the parameter burden.

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?

States a specific resource and scope ('who reaches one project') and enumerates the returned fields: user_id, email, role and reach mechanism. It also distinguishes the two access paths (organisation vs project), which separates it from list_organisation_members without naming it.

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 prerequisites ('Needs projects.read'), the upstream source of the id ('project_id comes from list_projects'), and the negative case ('a project the caller cannot reach answers not found'). No explicit sibling comparison to list_organisation_members, which is the closest alternative for access questions.

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

All Ankra 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