Skip to main content
Glama
Sign In

Dropspace

by io.github.JCLVSH
OverviewDiscussionsAdmin

get_batch_launch_analytics

Read-only

get cached analytics for multiple launches in one request (no live refresh, max 100 IDs)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ids": "<ids>"
    },
    "name": "get_batch_launch_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYeslaunch IDs to fetch analytics for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive behavior, and the description adds the genuinely useful trait that results come from cache with no live refresh, which affects data freshness decisions. It stops short of describing result shape or partial-failure behavior for missing IDs.

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?

A single front-loaded sentence with the batch scope first and the caching caveat immediately after. The 'max 100 IDs' clause mildly duplicates the schema constraint but is cheap and reinforces the limit inline.

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?

For a read-only, single-parameter batch fetch with no output schema, the definition covers the essentials: what it returns (cached analytics), for how many resources, and the limit. Only error behavior for invalid or unknown IDs is left unstated.

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 coverage is 100% for the single 'ids' parameter, and the description largely restates what the schema already declares (batch of launch IDs, max 100). No added meaning about ID validity, ordering, or what happens with unknown IDs.

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 states a specific verb and resource ('get cached analytics') plus a clear scope ('multiple launches in one request'), which separates it from the singular get_launch_analytics sibling. It never names that sibling, but the batch framing makes the distinction legible.

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?

'no live refresh' implicitly tells the agent this is not the tool for fresh data and points toward a single-launch live alternative, but no alternative is named and no explicit when-to-use condition is given. Usage is inferable rather than stated.

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

All Dropspace toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources