Skip to main content
Glama

misp_get_organisation

Retrieve detailed information about a MISP organisation using its unique ID.

Instructions

Get details of a specific MISP organisation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orgIdYesOrganisation ID

Implementation Reference

  • Handler for the 'misp_get_organisation' tool. Calls client.getOrganisation(orgId) and returns the organisation details as JSON, or an error message on failure.
    // Get organisation details
    server.tool(
      "misp_get_organisation",
      "Get details of a specific MISP organisation",
      {
        orgId: z.string().describe("Organisation ID"),
      },
      async ({ orgId }) => {
        try {
          const org = await client.getOrganisation(orgId);
          return {
            content: [{ type: "text", text: JSON.stringify(org, null, 2) }],
          };
        } catch (err) {
          return {
            content: [
              {
                type: "text",
                text: `Error getting organisation: ${err instanceof Error ? err.message : String(err)}`,
              },
            ],
            isError: true,
          };
        }
      }
    );
  • Input schema for the tool: accepts 'orgId' (required string) as defined via Zod.
    {
      orgId: z.string().describe("Organisation ID"),
    },
  • Client method getOrganisation() that performs a GET request to /organisations/view/{orgId} and returns the Organisation object.
    async getOrganisation(orgId: string): Promise<MispOrganisation> {
      const data = await this.request<{ Organisation: MispOrganisation }>(
        "GET",
        `/organisations/view/${encodeId(orgId, "orgId")}`
      );
      return data.Organisation;
    }
  • MispOrganisation interface defining the shape of the returned organisation object.
    export interface MispOrganisation {
      id: string;
      name: string;
      uuid: string;
      description: string;
      nationality: string;
      sector: string;
      type: string;
      local: boolean;
    }
  • src/index.ts:41-42 (registration)
    Registration of organisation tools (including misp_get_organisation) via registerOrganisationTools(server, client) in the main entry point.
    registerOrganisationTools(server, client);
    registerServerTools(server, client);
Behavior2/5

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

No annotations provided, and the description only says 'Get details', implying read-only but lacks specifics on permissions, rate limits, or response content.

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?

Single sentence, 8 words, front-loaded with action. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema or annotations, the description is minimal but sufficient for a simple single-parameter tool. Could include what details are returned.

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% with description 'Organisation ID'; description adds no extra meaning beyond what the schema already provides.

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 verb 'Get' and the resource 'details of a specific MISP organisation', distinguishing it from sibling tool misp_list_organisations which lists all organisations.

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 like misp_list_organisations or other get tools. No explicit 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/solomonneas/misp-mcp'

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