Skip to main content
Glama
Sign In

Pineprompt

by com.pineprompt
OverviewDiscussionsAdmin

List Users Tool

list-users-tool
Read-onlyIdempotent

List the members of an organization, ordered by name. Returns up to 50 per page; follow nextCursor to fetch additional pages.

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": {
      "organization_id": "<organization_id>"
    },
    "name": "list-users-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoOpaque pagination cursor. Omit on the first call; pass the `nextCursor` value from the previous response to fetch the next page.
organization_idYesThe numeric id of the organization whose members should be listed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful behavior the annotations do not: results are sorted by name, capped at 50 per page, and expanded by following `nextCursor`.

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?

Two short sentences with no filler, and the core purpose is front-loaded before the pagination detail. Every clause contributes either scope or an operational constraint.

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 two-parameter read-only list tool with rich annotations and no output schema, the description covers purpose, ordering, and pagination adequately. It stops short of describing what fields each member record contains, which is a minor gap given no output schema exists.

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 both parameters are already documented and a baseline of 3 applies. The description goes slightly beyond the schema by disclosing the 50-item page size, which tells the agent what to expect from `cursor`/`nextCursor` handling beyond the schema's opaque-cursor note.

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 uses a specific verb and resource ('List the members of an organization') plus an ordering rule, so an agent knows exactly what is returned. It does not explicitly distinguish itself from siblings such as list-organizations-tool, which lists organizations rather than their members, leaving that separation to the resource noun.

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?

Usage is implied by the resource ('members of an organization'), and the pagination instruction gives practical guidance for repeated calls. There is no explicit statement of when to prefer this over an alternative tool or of any preconditions beyond the required organization id.

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

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