Skip to main content
Glama
lincalinca

Crescender MCP Server

by lincalinca

get_loans_for_asset

Retrieve loan history for a specific asset by providing its UUID. Returns loan details embedded in the asset record.

Instructions

Get the loan history for a single asset. Currently returns whatever loans field is embedded on the asset detail; in a future version may paginate independently.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asset_idYesAsset uuid.

Implementation Reference

  • The full ToolDef for 'get_loans_for_asset': defines the name, description, inputSchema (asset_id required), and the async handler that calls GET /v1/schools/{schoolId}/gear/{id} and returns the loan history (current_loan and loans array) from the asset detail.
    const getLoansForAsset: ToolDef = {
      name: 'get_loans_for_asset',
      description:
        'Get the loan history for a single asset. Currently returns whatever loans field is embedded on the asset detail; in a future version may paginate independently.',
      inputSchema: {
        type: 'object',
        properties: {
          asset_id: { type: 'string', description: "Asset uuid." },
        },
        required: ['asset_id'],
        additionalProperties: false,
      },
      async handler(args, client) {
        const id = String(args.asset_id ?? '');
        if (!id) throw new Error('asset_id is required');
        const ctx = await client.getContext();
        const detail = (await client.get<{ current_loan?: unknown; loans?: unknown[] }>(
          `/v1/schools/${ctx.schoolId}/gear/${id}`,
        )) as { current_loan?: unknown; loans?: unknown[] };
        return {
          asset_id: id,
          current_loan: detail.current_loan ?? null,
          loans: detail.loans ?? [],
        };
      },
    };
  • Input schema for 'get_loans_for_asset': expects an object with required 'asset_id' (string) and no additional properties.
    inputSchema: {
      type: 'object',
      properties: {
        asset_id: { type: 'string', description: "Asset uuid." },
      },
      required: ['asset_id'],
      additionalProperties: false,
    },
  • The tool is registered in the exported 'tools' array (line 197) and also added to the 'toolByName' map (line 202) used by the MCP server to dispatch calls by name.
    export const tools: ToolDef[] = [
      listSchools,
      getAsset,
      searchAssets,
      getLoansForAsset,
      listMembers,
      listAssetThreads,
    ];
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses current behavior (returns embedded loans field) and a future change (independent pagination), adding valuable context beyond the schema. However, it omits details like whether the operation is read-only or any authorization needs.

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 succinct sentences: the first states the core purpose, the second adds behavioral nuance. Every sentence is purposeful with no redundancy.

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 simple tool with one parameter and no output schema, the description covers the function and current behavior. It could be slightly more complete by hinting at the format of the loan history, but the note about the embedded field provides reasonable context.

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 already describes the single parameter 'asset_id' as 'Asset uuid.' The description adds no further parameter semantics, so it meets the baseline of 3 given 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 'Get the loan history for a single asset,' specifying the action (get) and resource (loan history for asset). This distinguishes it from siblings like get_asset (general details) and list_asset_threads (threads).

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?

The description implies use when loan history for a single asset is needed, but offers no explicit when-to or when-not-to use compared to alternatives. No sibling tools serve the same purpose, so context is clear but guidelines are absent.

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