Skip to main content
Glama
Sign In

ShockAtlas

by com.shockatlas
OverviewDiscussionsAdmin

Export one signal (members)

get_export
Read-onlyIdempotent

With a member key: three signed links, valid seven days, to the complete export of one signal (bundle.json with the full dossier, counter-analysis and every series; organisations.csv; series.csv). Without a key it answers MEMBER_KEY_REQUIRED with the Premium plan.

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": {
      "slug": "<slug>"
    },
    "name": "get_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoA member key (dfk1…), issued with the plan; omit it for the free sample
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Beyond the read-only, idempotent annotations, the description discloses link count, validity period, bundle contents, and the MEMBER_KEY_REQUIRED error tied to the Premium plan. That is useful behavioral context, though it says nothing about rate limits, download size, or whether links can be regenerated.

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 dense sentences front-load the key requirement and then list the export contents efficiently. The parenthetical file list is informational rather than wasteful, and there is no filler text.

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 appropriately explains what the call returns: three signed links, their seven-day validity, and the bundle components. It is nearly complete for a simple two-parameter retrieval tool, but the key-omission behavior is ambiguous against the schema.

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?

The key parameter's behavior is partly described through the MEMBER_KEY_REQUIRED error, but this conflicts with the schema's statement that omitting the key yields a free sample. The description also adds no meaning for the required slug parameter, leaving half the parameters unreconciled.

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 resource and outcome: signed links to the complete export of one signal, with the exact bundle contents named. It is distinguishable from siblings like get_dossier and get_series because it describes a downloadable export rather than a single component.

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?

It tells the agent that a member key is needed and what happens without one, but it does not explicitly say when to choose this export over get_dossier or get_series. The usage context is implied by 'export' and the linked bundle contents rather than stated as a routing rule.

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

All ShockAtlas 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