Skip to main content
Glama

Find Project Member

find_project_member
Read-onlyIdempotent

Search for users with access to a MantisBT project by name, display name, or email to identify team members and assign tasks.

Instructions

Search for users with access to a MantisBT project by name, display name, or email.

Returns up to limit matching users (default: 10, max: 100). Matching is case-insensitive substring search across name, real_name, and email fields. Omit query to list the first limit users.

Data is served from the local metadata cache when fresh; falls back to a live API call otherwise.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesNumeric project ID
queryNoCase-insensitive substring to match against name, real_name, or email
limitNoMaximum number of results to return (default: 10, max: 100)

Implementation Reference

  • The handler logic for the 'find_project_member' tool, which fetches project users from cache or API and filters them based on the query.
      async ({ project_id, query, limit }) => {
        try {
          let users: MantisUser[];
          const cached = cache ? await cache.loadIfValid() : null;
          if (cached?.byProject[project_id]) {
            users = cached.byProject[project_id]!.users;
          } else {
            const result = await client.get<{ users: MantisUser[] }>(`projects/${project_id}/users`);
            users = result.users ?? [];
          }
          if (query) {
            const q = query.toLowerCase();
            users = users.filter((u) =>
              u.name.toLowerCase().includes(q) ||
              (u.real_name?.toLowerCase().includes(q) ?? false) ||
              (u.email?.toLowerCase().includes(q) ?? false)
            );
          }
          return {
            content: [{ type: 'text', text: JSON.stringify(users.slice(0, limit), null, 2) }],
          };
        } catch (error) {
          const msg = error instanceof Error ? error.message : String(error);
          return { content: [{ type: 'text', text: errorText(msg) }], isError: true };
        }
      }
    );
  • Registration and schema definition for the 'find_project_member' tool.
      server.registerTool(
        'find_project_member',
        {
          title: 'Find Project Member',
          description: `Search for users with access to a MantisBT project by name, display name, or email.
    
    Returns up to \`limit\` matching users (default: 10, max: 100). Matching is case-insensitive substring search across \`name\`, \`real_name\`, and \`email\` fields. Omit \`query\` to list the first \`limit\` users.
    
    Data is served from the local metadata cache when fresh; falls back to a live API call otherwise.`,
          inputSchema: z.object({
            project_id: z.coerce.number().int().positive().describe('Numeric project ID'),
            query: z.string().optional().describe('Case-insensitive substring to match against name, real_name, or email'),
            limit: z.coerce.number().int().min(1).max(100).default(10).describe('Maximum number of results to return (default: 10, max: 100)'),
          }),
          annotations: {
            readOnlyHint: true,
            destructiveHint: false,
            idempotentHint: true,
          },
        },
Behavior4/5

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

Annotations declare readOnly/idempotent/destructive hints. Description adds valuable behavioral context beyond annotations: case-insensitive substring matching logic, default/max limit constraints (10/100), and caching behavior (local metadata cache with fallback to live API). No contradictions with annotations.

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?

Three well-structured sentences: purpose statement upfront, behavioral constraints and limits in the middle, implementation detail (caching) last. Every sentence earns its place with zero redundancy or fluff.

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 3-parameter search tool without output schema, description adequately covers return behavior (up to limit matching users) and search semantics. Missing explicit field list of returned user objects, but mentions searchable fields which provides partial context. Caching disclosure is a nice completeness touch.

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?

With 100% schema coverage, baseline is met. Description adds meaningful usage context: explains that omitting 'query' changes behavior to listing first N users, and clarifies that matching spans multiple fields (name, real_name, email). This semantic context aids agent decision-making beyond raw schema.

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?

Description uses specific verb 'Search' with clear resource 'users with access to a MantisBT project' and specifies search fields (name, display name, email). Distinct from sibling 'get_project_users' by emphasizing the search/filter capability rather than retrieval of all users.

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?

Provides clear guidance on parameter interaction: 'Omit `query` to list the first `limit` users.' This explains how to use the tool for listing versus searching. Lacks explicit mention of when to use sibling 'get_project_users' instead, but implies usage through search-specific description.

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/dpesch/mantisbt-mcp-server'

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