Skip to main content
Glama
elmapicms

elmapicms-mcp-server

Official
by elmapicms

Get Project

get_project

Retrieve details of the active ElmapiCMS project to view its configuration and settings.

Instructions

Get information about the current ElmapiCMS project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:35-35 (registration)
    Calls registerProjectTools to register the 'get_project' tool on the MCP server.
    registerProjectTools(server, client);
  • Registers the 'get_project' tool and provides the async handler that calls client.get('/') to fetch project info from the ElmapiCMS API.
    export function registerProjectTools(
      server: McpServer,
      client: ElmapiClient
    ): void {
      server.registerTool("get_project", {
        title: "Get Project",
        description: "Get information about the current ElmapiCMS project",
      }, async () => {
        const result = await client.get("/");
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
        };
      });
    }
  • The ElmapiClient.get() method used by the handler to make a GET request to the API root endpoint.
    async get(
      path: string,
      params?: Record<string, unknown>
    ): Promise<unknown> {
      const url = new URL(`${this.baseUrl}${path}`);
      if (params) {
        const flatPairs = this.flattenParams(params);
        for (const [key, value] of flatPairs) {
          url.searchParams.append(key, value);
        }
      }
    
      const response = await fetch(url.toString(), {
        method: "GET",
        headers: this.headers(),
      });
    
      return this.handleResponse(response);
    }
Behavior2/5

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

No annotations provided, so the description must disclose behavioral traits. It only says 'Get information', implying a read operation, but fails to mention side effects, performance, authentication needs, or what 'current' means.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, no waste. Could be improved by adding a bit more detail without becoming verbose.

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?

With no output schema and a sparse description, the agent lacks information about what 'information' includes. For a no-parameter tool, more context about the return value is needed.

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 input schema has zero parameters, so the description cannot add meaning. Baseline of 4 is appropriate since no additional description is needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get' and the resource 'the current ElmapiCMS project', distinguishing it from siblings like get_collection or get_entry. However, 'information' is vague; specifying 'metadata' or 'details' would be more precise.

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?

No guidance on when to use this tool versus alternatives such as get_collection or get_entry. The description does not mention any prerequisites or context for selection.

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

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