Skip to main content
Glama
Sign In
vish288

mcp-coda

by vish288
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Coda Get Pack Analytics Summary

coda_get_pack_analytics_summary
Read-onlyIdempotent

Retrieve aggregated analytics for Coda packs, including total installs, doc usage, and formula invocations, filtered by date and publication status.

Instructions

Get aggregated analytics summary for packs.

Returns total installs, doc usage, and formula invocations summed across packs. Only available to pack makers.

Input Schema

NameRequiredDescriptionDefault
pack_idsNoFilter to specific pack IDs
since_dateNoStart date for analytics (ISO 8601)
until_dateNoEnd date for analytics (ISO 8601)
is_publishedNoFilter to published (True) or unpublished (False) packs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.1
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. First observedv0.4.14

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/openWorldHint/idempotentHint, so the safety profile is covered. The description adds real value beyond that: it specifies the access restriction (pack makers only) and the aggregated nature of the result, which an agent cannot derive from the structured fields.

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?

Two short sentences with zero filler, and the core action is front-loaded ahead of the return-value detail and access note. Nothing is padded, though the layout is slightly fragmented across lines.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by naming the returned aggregates (installs, doc usage, formula invocations) and stating the access restriction. Combined with the fully documented schema, an agent has enough to invoke it correctly, though the missing distinction from coda_list_pack_analytics is a residual gap.

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 description coverage is 100%, so all four parameters (pack_ids, since_date, until_date, is_published) are fully documented in the schema. The description adds no further parameter meaning, so the baseline 3 applies.

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?

States a specific verb+resource: 'aggregated analytics summary for packs,' and enumerates the metrics returned (installs, doc usage, formula invocations). It implicitly distinguishes from the sibling coda_list_pack_analytics by emphasizing aggregation/summary, though it never names that sibling.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The prerequisite 'Only available to pack makers' is clear and useful context for eligibility. However, there is no explicit when-to-use guidance versus the closely related coda_list_pack_analytics or coda_get_analytics_updated, leaving the agent to infer the distinction between summary and list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools