Skip to main content
Glama

maasy_get_daily_summary

Retrieve a daily summary of operations covering recent events, items needing attention, and suggested actions for a brand project.

Instructions

Today's operations summary: what happened, what needs attention, recommended actions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNoBrand UUID

Implementation Reference

  • src/index.ts:272-277 (registration)
    Registration of the 'maasy_get_daily_summary' MCP tool. Defines name, description, schema (optional project_id), and links to the handler 'get_daily_summary'.
    server.tool(
      "maasy_get_daily_summary",
      "Today's operations summary: what happened, what needs attention, recommended actions.",
      { project_id: z.string().optional().describe("Brand UUID") },
      toolHandler("get_daily_summary")
    );
  • Input schema for the tool: one optional string parameter 'project_id' (the Brand UUID). Zod validation.
    { project_id: z.string().optional().describe("Brand UUID") },
  • Generic toolHandler wrapper. For 'maasy_get_daily_summary', it calls callGateway('get_daily_summary', args) which delegates to the Supabase edge function 'mcp-gateway'.
    function toolHandler(toolName: string, argsFn?: (args: Record<string, unknown>) => Record<string, unknown>) {
      return async (args: Record<string, unknown>) => {
        try {
          const gatewayArgs = argsFn ? argsFn(args) : args;
          // Auto-inject default project_id if not provided
          if (DEFAULT_PROJECT_ID && !gatewayArgs.project_id) {
            gatewayArgs.project_id = DEFAULT_PROJECT_ID;
          }
          const result = await callGateway(toolName, gatewayArgs);
          return { content: [{ type: "text" as const, text: JSON.stringify(result, null, 2) }] };
        } catch (e: unknown) {
          return {
            content: [{ type: "text" as const, text: `Error: ${e instanceof Error ? e.message : String(e)}` }],
            isError: true,
          };
        }
      };
    }
  • Helper that performs the actual HTTP call to the Supabase edge function. Sends { tool: 'get_daily_summary', args } to the mcp-gateway endpoint.
    export async function callGateway(tool: string, args: Record<string, unknown> = {}): Promise<unknown> {
      const res = await fetch(gatewayUrl, {
        method: "POST",
        headers: {
          "Content-Type": "application/json",
          [authHeader.name]: authHeader.value,
        },
        body: JSON.stringify({ tool, args }),
      });
    
      const data = await res.json();
    
      if (!res.ok) {
        throw new Error(data.error || `Gateway error (${res.status})`);
      }
    
      return data.result;
    }
Behavior2/5

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

With no annotations, the description bears full responsibility for disclosing behavior. It does not mention whether the tool is read-only, requires authentication, or has any side effects. The mention of 'recommended actions' is vague and does not clarify if the tool actually performs actions or just suggests them.

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 at 10 words, covering the key aspects: events ('what happened'), attention items, and recommendations. It is well-structured as a single sentence, though it could benefit from 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?

Given the lack of an output schema, the description should thoroughly explain the return format. It provides a high-level idea of the content but omits details like timezone, data granularity, and whether the summary is per brand or aggregated. The optional parameter's impact on the output is also not clarified.

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 provides a description for the single parameter ('Brand UUID'), achieving 100% coverage. The tool description does not add any additional meaning, such as whether the parameter is optional, how to obtain the UUID, or what happens if omitted. Since the schema already documents the parameter, a 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 that the tool provides a summary of today's operations including events, attention items, and recommended actions. However, it does not differentiate itself from sibling tools like maasy_get_alerts or maasy_get_crm_summary, which may offer similar summaries.

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 is provided on when to use this tool versus alternatives. For example, it doesn't explain under what circumstances to use the daily summary instead of maasy_get_alerts for attention items or maasy_get_crm_summary for operational updates.

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

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