Skip to main content
Glama
abutbul

Gatherings MCP Server

by abutbul

show_gathering

Display details of a social gathering to track expenses and calculate reimbursements for settling balances between friends.

Instructions

Show details of a gathering

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gathering_idYesID of the gathering to display

Implementation Reference

  • Executes the 'show_gathering' tool by validating the gathering_id argument and constructing the shell command to run the Python script's 'show' subcommand.
    case 'show_gathering':
      if (!isGatheringIdArg(args)) {
        throw new McpError(ErrorCode.InvalidParams, 'Invalid show_gathering arguments');
      }
      command += ` show "${args.gathering_id}"`;
      break;
  • Defines the input schema for the 'show_gathering' tool, requiring a 'gathering_id' string.
    inputSchema: {
      type: 'object',
      properties: {
        gathering_id: {
          type: 'string',
          description: 'ID of the gathering to display',
        },
      },
      required: ['gathering_id'],
  • src/index.ts:162-175 (registration)
    Registers the 'show_gathering' tool in the MCP server's tool list, including name, description, and schema.
    {
      name: 'show_gathering',
      description: 'Show details of a gathering',
      inputSchema: {
        type: 'object',
        properties: {
          gathering_id: {
            type: 'string',
            description: 'ID of the gathering to display',
          },
        },
        required: ['gathering_id'],
      },
    },
  • Type guard helper function used to validate arguments for tools requiring a 'gathering_id', including 'show_gathering'.
    const isGatheringIdArg = (args: any): args is { gathering_id: string } =>
      typeof args === 'object' && args !== null &&
      typeof args.gathering_id === 'string';
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it 'shows details' without disclosing behavioral traits. It doesn't mention if this is a read-only operation, what permissions are needed, how errors are handled, or the format/scope of returned details, leaving significant gaps.

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?

The description is a single, efficient sentence with no wasted words. However, it's front-loaded but lacks depth, making it concise but potentially under-specified for a tool with no annotations or output schema.

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 complexity (a read operation with no annotations, no output schema, and 1 parameter), the description is incomplete. It doesn't explain what details are shown, the return format, or error conditions, making it inadequate for an agent to use this tool effectively without guesswork.

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 schema description coverage is 100%, with the parameter 'gathering_id' fully documented in the schema. The description adds no additional meaning beyond the schema, such as examples or context for the ID, so it meets the baseline of 3 where the schema does the heavy lifting.

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

Purpose3/5

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

The description 'Show details of a gathering' clearly states the verb ('show') and resource ('gathering'), but it's vague about what specific details are shown. It doesn't distinguish this tool from siblings like 'list_gatherings' or 'create_gathering' beyond the basic action.

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. It doesn't mention prerequisites (e.g., needing a gathering_id), exclusions, or comparisons to siblings like 'list_gatherings' for overviews or 'create_gathering' for setup.

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/abutbul/gatherings-mcp'

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