Skip to main content
Glama

log_daily_metrics

Record daily sales activity metrics including outreach attempts, responses, calls booked, proposals sent, deals closed, and revenue generated for revenue tracking and analysis.

Instructions

Log daily activity metrics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoYYYY-MM-DD
outreachAttemptsNo
responsesNo
callsBookedNo
proposalsSentNo
dealsClosedNo
revenueClosedNo

Implementation Reference

  • Handler implementation for the 'log_daily_metrics' tool. Delegates execution to the callAPI function with action 'logMetric' and tool arguments.
    case "log_daily_metrics":
      result = await callAPI("logMetric", args);
      break;
  • Input schema and registration for the 'log_daily_metrics' tool in the ListTools response, defining parameters for daily metrics logging.
    {
      name: "log_daily_metrics",
      description: "Log daily activity metrics",
      inputSchema: {
        type: "object",
        properties: {
          date: { type: "string", description: "YYYY-MM-DD" },
          outreachAttempts: { type: "number" },
          responses: { type: "number" },
          callsBooked: { type: "number" },
          proposalsSent: { type: "number" },
          dealsClosed: { type: "number" },
          revenueClosed: { type: "number" },
        },
      },
    },
  • index.js:310-325 (registration)
    Registration of the 'log_daily_metrics' tool within the server's tool list.
    {
      name: "log_daily_metrics",
      description: "Log daily activity metrics",
      inputSchema: {
        type: "object",
        properties: {
          date: { type: "string", description: "YYYY-MM-DD" },
          outreachAttempts: { type: "number" },
          responses: { type: "number" },
          callsBooked: { type: "number" },
          proposalsSent: { type: "number" },
          dealsClosed: { type: "number" },
          revenueClosed: { type: "number" },
        },
      },
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Log' implies a write operation, but it does not specify if this creates new records, updates existing ones, requires authentication, has side effects, or handles errors. This leaves critical behavioral traits unclear for a tool with 7 parameters.

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, making it appropriately concise. However, it is front-loaded with minimal information, which limits usefulness despite its brevity.

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 tool's complexity (7 parameters, no annotations, no output schema), the description is incomplete. It fails to explain the tool's behavior, parameter interactions, or expected outcomes, leaving significant gaps for effective agent use.

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 description coverage is low at 14%, with only the 'date' parameter documented. The description does not explain the meaning of parameters like 'outreachAttempts' or 'revenueClosed', nor does it clarify relationships between them (e.g., if 'callsBooked' is a subset of 'responses'). It adds no semantic value beyond the basic schema.

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

Purpose2/5

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

The description 'Log daily activity metrics' restates the tool name 'log_daily_metrics' with minimal elaboration, making it tautological. It specifies the action ('log') and resource ('daily activity metrics') but lacks detail on what 'log' entails (e.g., create, update, store) or how it differs from sibling tools like 'log_outreach' or 'matrix_daily_summary', leaving purpose vague.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 does not mention prerequisites, context (e.g., daily reporting), or exclusions, and fails to differentiate from similar tools like 'log_outreach' or 'matrix_daily_summary', offering no usage instructions.

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/PromptishOperations/mcpSpec'

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