Skip to main content
Glama
dalboki

sonsuchup-mcp

by dalboki

add_record

Add a record to a case, specifying content and optional time to document events in the mystery timeline.

Instructions

사건 기록을 추가합니다. time은 datetime-local 문자열 (예: "2026-04-20T14:30") 또는 생략(시간 미지정).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
caseIdYes
timeNo
contentYes

Implementation Reference

  • The 'add_record' tool handler function. Fetches the case, generates a new localId, pushes a new record object (with id, time, content, selected=false) onto c.records, then saves and returns { localId, url }.
    handler: async (input: { caseId: string; time?: string; content: string }) => {
      const c = await fetchCase(input.caseId);
      const localId = nextLocalId(c.records);
      c.records.push({
        id: localId,
        time: input.time ?? '',
        content: input.content,
        selected: false,
      });
      await saveCase(c);
      return { localId, url: caseUrl(input.caseId) };
    },
  • Input schema for 'add_record' using Zod: requires caseId (UUID), optional time (string), and required content (string min length 1).
    inputSchema: z.object({
      caseId: z.string().uuid(),
      time: z.string().optional(),
      content: z.string().min(1),
    }),
  • src/tools.ts:253-274 (registration)
    The 'add_record' tool definition object in the tools array. Contains name, description, inputSchema, and handler.
    {
      name: 'add_record',
      description:
        '사건 기록을 추가합니다. time은 datetime-local 문자열 (예: "2026-04-20T14:30") 또는 생략(시간 미지정).',
      inputSchema: z.object({
        caseId: z.string().uuid(),
        time: z.string().optional(),
        content: z.string().min(1),
      }),
      handler: async (input: { caseId: string; time?: string; content: string }) => {
        const c = await fetchCase(input.caseId);
        const localId = nextLocalId(c.records);
        c.records.push({
          id: localId,
          time: input.time ?? '',
          content: input.content,
          selected: false,
        });
        await saveCase(c);
        return { localId, url: caseUrl(input.caseId) };
      },
    },
  • Helper function nextLocalId used by the handler to generate the next incremental local ID for records.
    function nextLocalId(items: { id: number }[]): number {
      return items.reduce((max, it) => Math.max(max, it.id ?? 0), 0) + 1;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions the action ('add') implying mutation, but does not disclose side effects, permissions required, idempotency, or error behavior. The only behavioral detail is that time can be omitted.

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 concise: one sentence stating the purpose followed by a clarifying note on the time parameter. It is front-loaded with the core action. No wasted words.

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 no output schema, no annotations, and three parameters, the description is insufficient. It omits return behavior, data constraints for content, and the overall scope of 'record'. An agent would lack enough context to use this tool effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate. It explains the time parameter (format and optionality), but says nothing about caseId (required it is) or content (required, minLength). The description adds value for time only, leaving two parameters unaddressed.

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 it adds a case record. It uses a specific verb and resource ('add record'), but does not differentiate from sibling tools like add_alibi or add_person, which are more specific record types. The clarity is good but could be more distinguishing.

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 a guideline for the time parameter format ('datetime-local string'), but lacks any guidance on when to use this tool versus alternatives (e.g., add_alibi for alibis). No context on prerequisites or typical use cases is given.

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/dalboki/sonsuchup-mcp'

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