Skip to main content
Glama
lincalinca

Crescender MCP Server

by lincalinca

search_assets

Search school assets by free-text query or filters on class, category, or status. Returns up to 50 matches per page with pagination support.

Instructions

Search the school's assets by free-text query and/or filters. Returns up to 50 matches per page. Use the cursor field from the response to fetch the next page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFree-text query (matches name, model, serial).
item_classNoFilter by class: 'instrument', 'equipment', 'consumable', etc.
categoryNoDomain category (e.g. 'brass', 'percussion', 'av').
statusNoLifecycle: 'active', 'retired', 'in_repair', etc.
cursorNoOpaque pagination cursor from a prior response.

Implementation Reference

  • The async handler function that executes the 'search_assets' tool logic. It calls the API endpoint /v1/schools/{schoolId}/gear with optional query parameters (q, item_class, category, status, cursor) and a limit of 50.
    async handler(args, client) {
      const ctx = await client.getContext();
      return client.get<unknown>(`/v1/schools/${ctx.schoolId}/gear`, {
        q: typeof args.q === 'string' ? args.q : undefined,
        item_class: typeof args.item_class === 'string' ? args.item_class : undefined,
        category: typeof args.category === 'string' ? args.category : undefined,
        status: typeof args.status === 'string' ? args.status : undefined,
        cursor: typeof args.cursor === 'string' ? args.cursor : undefined,
        limit: '50',
      });
    },
  • Input schema for the search_assets tool. Defines the 'q' (free-text query), 'item_class', 'category', 'status', and 'cursor' (pagination) parameters with descriptions.
    inputSchema: {
      type: 'object',
      properties: {
        q: { type: 'string', description: 'Free-text query (matches name, model, serial).' },
        item_class: {
          type: 'string',
          description: "Filter by class: 'instrument', 'equipment', 'consumable', etc.",
        },
        category: {
          type: 'string',
          description: "Domain category (e.g. 'brass', 'percussion', 'av').",
        },
        status: {
          type: 'string',
          description: "Lifecycle: 'active', 'retired', 'in_repair', etc.",
        },
        cursor: { type: 'string', description: 'Opaque pagination cursor from a prior response.' },
      },
      additionalProperties: false,
    },
  • Tool definition for 'search_assets' including name, description, input schema, and handler. Exported via the 'tools' array and 'toolByName' map at lines 193-202.
    const searchAssets: ToolDef = {
      name: 'search_assets',
      description:
        "Search the school's assets by free-text query and/or filters. Returns up to 50 matches per page. Use the `cursor` field from the response to fetch the next page.",
      inputSchema: {
        type: 'object',
        properties: {
          q: { type: 'string', description: 'Free-text query (matches name, model, serial).' },
          item_class: {
            type: 'string',
            description: "Filter by class: 'instrument', 'equipment', 'consumable', etc.",
          },
          category: {
            type: 'string',
            description: "Domain category (e.g. 'brass', 'percussion', 'av').",
          },
          status: {
            type: 'string',
            description: "Lifecycle: 'active', 'retired', 'in_repair', etc.",
          },
          cursor: { type: 'string', description: 'Opaque pagination cursor from a prior response.' },
        },
        additionalProperties: false,
      },
      async handler(args, client) {
        const ctx = await client.getContext();
        return client.get<unknown>(`/v1/schools/${ctx.schoolId}/gear`, {
          q: typeof args.q === 'string' ? args.q : undefined,
          item_class: typeof args.item_class === 'string' ? args.item_class : undefined,
          category: typeof args.category === 'string' ? args.category : undefined,
          status: typeof args.status === 'string' ? args.status : undefined,
          cursor: typeof args.cursor === 'string' ? args.cursor : undefined,
          limit: '50',
        });
      },
    };
  • The tools array and toolByName map that register all tools including search_assets for use by the MCP server.
    export const tools: ToolDef[] = [
      listSchools,
      getAsset,
      searchAssets,
      getLoansForAsset,
      listMembers,
      listAssetThreads,
    ];
    
    export const toolByName = new Map(tools.map((t) => [t.name, t]));
Behavior3/5

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

No annotations exist, so the description bears full burden. It discloses pagination (50 per page, cursor) but omits auth requirements, response structure, and whether operations are read-only.

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 concise sentences: first defines purpose, second covers pagination. No wasted words.

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

Completeness2/5

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

Despite no output schema, the description fails to hint at the response shape (e.g., list of asset objects). Pagination is covered, but the overall completeness is lacking for a search tool with 5 optional parameters.

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 covers all parameters with descriptions; description adds no new semantic info beyond confirming free-text and filter usage, meeting the baseline for 100% schema coverage.

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 searches school assets by free-text query and filters, using a specific verb and resource, and distinguishes from siblings like get_asset (single asset) and list tools.

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?

Pagination guidance is provided, but no explicit advice on when to use this tool versus alternatives like get_asset for a specific asset or list_members for members.

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