Skip to main content
Glama

get_collection

Retrieve a collection's details by providing its name.

Instructions

Get a specific collection by name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCollection name

Implementation Reference

  • src/index.ts:48-55 (registration)
    Registration of the 'get_collection' tool using server.registerTool() — binds the tool name, schema, and handler together.
    server.registerTool(
      "get_collection",
      {
        description: "Get a specific collection by name",
        inputSchema: { name: z.string().describe("Collection name") },
      },
      async ({ name }) => ok(await nocoFetch(`/api/collections/${name}`))
    );
  • Handler function for get_collection — fetches a specific collection by name via GET /api/collections/{name}.
    async ({ name }) => ok(await nocoFetch(`/api/collections/${name}`))
  • Input schema for get_collection — uses Zod to define a required 'name' string parameter.
      inputSchema: { name: z.string().describe("Collection name") },
    },
  • Helper utility 'nocoFetch' used by the handler to make authenticated HTTP requests to the NocoBase API.
    async function nocoFetch(path: string, options: RequestInit = {}): Promise<unknown> {
      const url = `${NOCOBASE_URL}${path}`;
      const res = await fetch(url, {
        ...options,
        headers: { ...reqHeaders, ...(options.headers as Record<string, string> | undefined) },
      });
      const text = await res.text();
      if (!res.ok) throw new Error(`HTTP ${res.status} ${res.statusText}: ${text}`);
      try { return JSON.parse(text); } catch { return text; }
    }
  • Helper function 'ok' used by the handler to format successful responses as text content.
    const ok = (data: unknown) => ({
      content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }],
    });
Behavior2/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 only states it retrieves a collection but does not disclose behaviors such as error handling (e.g., if name not found), idempotency, or permission requirements.

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?

A single, front-loaded sentence that efficiently conveys the tool's purpose with no wasted words.

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?

Given the tool's simplicity (one parameter, no output schema), the description is reasonably complete. It covers purpose and identification, though it could mention return format or error scenarios.

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 single parameter 'name' is fully described in the input schema ('Collection name'), and the description adds the contextual phrase 'by name'. With 100% schema coverage, the baseline is 3, and the description adds minimal extra meaning.

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 'Get a specific collection by name' clearly states the action (Get), resource (collection), and identifier (name). It effectively distinguishes from sibling 'list_collections' which retrieves multiple collections.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives or when not to use it. No exclusions or prerequisites are mentioned.

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/puguhsudarma/nocobase-mcp-server'

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