Skip to main content
Glama
lincalinca

Crescender MCP Server

by lincalinca

list_members

Retrieve a filtered list of school members including id, role, status, and external_id without personal identifiers. Supports filtering by role and status with pagination.

Instructions

List the school's members. Returns id, role, status, external_id only — no PII (email/phone are intentionally excluded from the public API).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleNoFilter by role: 'student', 'teacher', 'staff', etc.
statusNoLifecycle: 'active', 'inactive'.
cursorNoOpaque pagination cursor.

Implementation Reference

  • Handler function for list_members tool. Calls GET /v1/schools/{schoolId}/members with optional role, status, and cursor query parameters.
    const listMembers: ToolDef = {
      name: 'list_members',
      description:
        "List the school's members. Returns id, role, status, external_id only — no PII (email/phone are intentionally excluded from the public API).",
      inputSchema: {
        type: 'object',
        properties: {
          role: { type: 'string', description: "Filter by role: 'student', 'teacher', 'staff', etc." },
          status: { type: 'string', description: "Lifecycle: 'active', 'inactive'." },
          cursor: { type: 'string', description: 'Opaque pagination cursor.' },
        },
        additionalProperties: false,
      },
      async handler(args, client) {
        const ctx = await client.getContext();
        return client.get<unknown>(`/v1/schools/${ctx.schoolId}/members`, {
          role: typeof args.role === 'string' ? args.role : undefined,
          status: typeof args.status === 'string' ? args.status : undefined,
          cursor: typeof args.cursor === 'string' ? args.cursor : undefined,
        });
      },
    };
  • Input schema for list_members: optional role (string), status (string), cursor (string) filters.
    inputSchema: {
      type: 'object',
      properties: {
        role: { type: 'string', description: "Filter by role: 'student', 'teacher', 'staff', etc." },
        status: { type: 'string', description: "Lifecycle: 'active', 'inactive'." },
        cursor: { type: 'string', description: 'Opaque pagination cursor.' },
      },
      additionalProperties: false,
    },
  • Tool registration in the tools array and toolByName map, making list_members available for dispatch.
    export const tools: ToolDef[] = [
      listSchools,
      getAsset,
      searchAssets,
      getLoansForAsset,
      listMembers,
      listAssetThreads,
    ];
    
    export const toolByName = new Map(tools.map((t) => [t.name, t]));
  • src/server.ts:40-50 (registration)
    MCP server dispatch in src/server.ts — tools/call handler looks up the tool by name from toolByName map and calls its handler.
    // tools/call — dispatch by name; let errors bubble up as protocol
    // errors (the SDK serializes them appropriately).
    server.setRequestHandler(CallToolRequestSchema, async (req) => {
      const { name, arguments: args } = req.params;
      const tool = toolByName.get(name);
      if (!tool) {
        throw new Error(`Unknown tool: ${name}`);
      }
    
      try {
        const result = await tool.handler((args ?? {}) as Record<string, unknown>, client);
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It discloses the important exclusion of PII, but does not mention pagination behavior (cursor usage, limits), performance implications, or whether the list is ordered. This is a moderate gap for a list endpoint.

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 efficient sentences: first defines purpose, second adds critical behavioral caveat. No redundant information. Every sentence earns its place.

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

Completeness3/5

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

For a simple list tool with three optional parameters and no output schema, the description covers the basic purpose and a key constraint (no PII). However, it lacks details on pagination, ordering, and expected response format, which would be helpful without an output schema.

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?

The input schema covers all three parameters with descriptions. The tool description does not add any parameter-specific semantics beyond the schema. The only added value is about the output (returned fields), not parameters.

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 the tool lists school members and specifies the exact fields returned (id, role, status, external_id). It also explicitly excludes PII, setting clear expectations. This distinguishes it from sibling tools which focus on assets and loans.

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?

The context is clear: the tool is for listing members. Sibling tools are about assets and schools, so the usage context is implied. However, there is no explicit guidance on when to use this tool versus alternatives, nor any caveats about filtering or pagination.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lincalinca/crescender-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server