Skip to main content
Glama

get_meeting_location

Read-onlyIdempotent

Retrieve a specific meeting location by providing its ID. Access location details for scheduling or reference.

Instructions

Get an meeting location

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the meeting location to retrieve

Implementation Reference

  • The handler function for the 'get_meeting_location' tool. It calls apiGet with the meeting location ID, logs the response, and formats the result using formatShow.
    async ({ id }) => {
      try {
        const record = await apiGet<EduframeRecord>(`/meeting_locations/${id}`);
        void logResponse("get_meeting_location", { id }, record);
        return formatShow(record, "meeting location");
      } catch (error) {
        return formatError(error);
      }
    },
  • The input schema for 'get_meeting_location' - expects a single 'id' parameter (positive integer).
    description: "Get an meeting location",
    annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true },
    inputSchema: { id: z.number().int().positive().describe("ID of the meeting location to retrieve") },
  • Registration of the 'get_meeting_location' tool via server.registerTool, including its schema and handler.
    server.registerTool(
      "get_meeting_location",
      {
        description: "Get an meeting location",
        annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true },
        inputSchema: { id: z.number().int().positive().describe("ID of the meeting location to retrieve") },
      },
      async ({ id }) => {
        try {
          const record = await apiGet<EduframeRecord>(`/meeting_locations/${id}`);
          void logResponse("get_meeting_location", { id }, record);
          return formatShow(record, "meeting location");
        } catch (error) {
          return formatError(error);
        }
      },
    );
  • The registerAllTools function that invokes all tool registration functions, including registerMeetingLocationTools which registers 'get_meeting_location'.
    export function registerAllTools(server: McpServer): void {
      for (const register of tools) {
        register(server);
      }
    }
  • Imports used by the 'get_meeting_location' tool: zod for schema, apiGet for the API call, formatShow/formatError for response formatting, and logResponse for logging.
    import { z } from "zod";
    import type { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
    import { apiDelete, apiGet, apiList, apiPatch, apiPost } from "../api";
    import {
      formatCreate,
      formatDelete,
      formatError,
      formatList,
      formatShow,
      formatUpdate,
      type EduframeRecord,
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, which are consistent with the description. The description adds no additional behavioral context, but does not contradict the annotations.

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

Conciseness3/5

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

The description is very short (one sentence) and front-loaded, but contains a grammatical error. It is concise but lacks proper structure and completeness.

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?

Given the absence of an output schema, the description should explain what the tool returns, but it does not. The tool is simple but incomplete for a get operation without describing the response.

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 a single 'id' parameter described as 'ID of the meeting location to retrieve'. The description does not add any meaning beyond what the schema provides, so a baseline score of 3 is appropriate.

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 action (Get) and resource (meeting location), but has a grammatical error ('an meeting') and does not explicitly differentiate from the sibling 'get_meeting_locations' tool. However, the singular form hints at retrieving a specific location 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 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, such as 'get_meeting_locations' for listing all locations. No context or exclusions 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/martijnpieters/eduframe-mcp'

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