Skip to main content
Glama
lincalinca

Crescender MCP Server

by lincalinca

get_asset

Retrieve complete details for a single asset by its ID, including model, serial, location, role, and current loan status.

Instructions

Get full detail for a single asset (instrument, equipment, sub-item) by id. Includes model, serial, location, role, and the current loan if any.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asset_idYesAsset uuid (the gear's id field).

Implementation Reference

  • The handler function for the get_asset tool. Extracts the asset_id from args, validates it, resolves the school context, and makes a GET request to /v1/schools/{schoolId}/gear/{id}.
    async handler(args, client) {
      const id = String(args.asset_id ?? '');
      if (!id) throw new Error('asset_id is required');
      const ctx = await client.getContext();
      return client.get<unknown>(`/v1/schools/${ctx.schoolId}/gear/${id}`);
    },
  • The input schema for get_asset, defining asset_id as a required string property (the gear's UUID).
    inputSchema: {
      type: 'object',
      properties: {
        asset_id: {
          type: 'string',
          description: "Asset uuid (the gear's id field).",
        },
      },
      required: ['asset_id'],
      additionalProperties: false,
    },
  • Registration of getAsset in the tools array exported from the module.
    listSchools,
    getAsset,
  • The toolByName map which allows looking up get_asset by its name string.
    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?

Without annotations, the description carries the burden. It implies read-only but does not explicitly state non-destructive behavior, required permissions, or error cases. It adds value by mentioning the return of 'current loan'.

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?

The description is a single, front-loaded sentence with no wasted words. It effectively conveys the tool's purpose and scope.

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 read tool with one parameter and no output schema, the description lists key fields returned, covering the main use case. Could mention behavior when asset not found, but not critical.

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 coverage is 100% for the single parameter. The description adds context about what is returned but does not add parameter-level details beyond the schema. Baseline 3 is appropriate.

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 action ('Get full detail') and resource ('single asset'), and lists included fields. It distinguishes from siblings like 'search_assets' by focusing on retrieval by ID.

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 for single asset detail but lacks explicit guidance on when to use alternatives (e.g., search_assets for filtering). No exclusions or context provided.

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