Skip to main content
Glama
lincalinca

Crescender MCP Server

by lincalinca

list_schools

Retrieve the school bound to your token to confirm which school you are currently accessing before making other API calls.

Instructions

List schools accessible to the calling token. Each token is bound to exactly one school, so this returns a single-item array. Useful for the AI to confirm which school it's looking at before making other calls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes list_schools logic: resolves token context via client.getContext(), fetches the school by its ID from /v1/schools/{schoolId}, and returns a single-item array.
    async handler(_args, client) {
      const ctx = await client.getContext();
      const school = await client.get<unknown>(`/v1/schools/${ctx.schoolId}`);
      return { schools: [school] };
    },
  • Input schema for list_schools — an empty object with no properties and additionalProperties set to false, since the tool takes no arguments.
    inputSchema: {
      type: 'object',
      properties: {},
      additionalProperties: false,
    },
  • The tools array (line 193-200) registers listSchools alongside all other tools. The toolByName map (line 202) provides name-based lookup.
    // ─── exports ────────────────────────────────────────────────────────
    
    export const tools: ToolDef[] = [
      listSchools,
      getAsset,
      searchAssets,
      getLoansForAsset,
      listMembers,
      listAssetThreads,
    ];
  • The ApiClient.getContext() helper used by the handler to resolve the token's bound school ID, and ApiClient.get() method used to make the HTTP GET request.
    async getContext(): Promise<CallerContext> {
      if (this.context) return this.context;
      const data = await this.get<{
        school_id: string;
        school_name: string | null;
        capabilities: string[];
      }>('/v1/me');
      this.context = {
        schoolId: data.school_id,
        schoolName: data.school_name,
        capabilities: data.capabilities,
      };
      this.log.info('mcp:context:resolved', { ...this.context });
      return this.context;
    }
    
    async get<T>(path: string, query?: Record<string, string | undefined>): Promise<T> {
      const url = new URL(this.cfg.apiUrl + (path.startsWith('/') ? path : '/' + path));
      if (query) {
        for (const [k, v] of Object.entries(query)) {
          if (v !== undefined && v !== '') url.searchParams.set(k, v);
        }
      }
      return this.request<T>('GET', url);
    }
Behavior4/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It correctly discloses that the tool returns a single-item array due to token binding and implies it is a read-only operation, which is sufficient for a simple list tool.

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 sentences front-load the purpose and provide essential behavior details without any wasted words. Every sentence is informative.

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?

There is no output schema, but the description adequately explains that the result is a single-item array. For a simple, parameterless list tool, this provides sufficient context for an AI to understand and use the tool.

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?

The tool has zero parameters, and schema description coverage is 100% trivially. The description adds value by explaining the return behavior, which goes beyond the schema. Baseline for 0 parameters is 4.

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 schools accessible to the token, and explains the unique behavior that each token is bound to one school, returning a single-item array. This distinguishes it from sibling tools like get_asset or list_members, which serve different purposes.

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 description explicitly suggests using this tool 'to confirm which school it's looking at before making other calls,' providing clear context for when to invoke it. However, it does not mention when not to use it or alternatives.

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