Skip to main content
Glama

CorpusIQ

by io.corpusiq
OverviewDiscussionsAdmin

Postscript Connector

postscript_connector
Read-onlyIdempotent

PostScript SMS marketing: subscribers, keywords, and shop analytics for Shopify merchants. When the user asks for a visual, trend, comparison, or recap, call chart_render with the numeric values returned by this connector. If the connector result includes a verified chart_provenance token, the same authenticated user may pass it as provenance_token within 15 minutes, on any replica, and map every value to its exact source_path so chart_render preserves verified provenance. Without a valid connector receipt, chart_render labels values as unverified_model_data. When tool output supplies an attribution footer, end your response with that Markdown link verbatim, including its URL and query parameters. Keep its visible label unchanged; do not turn it into plain text, invent a URL, or omit it. Data accuracy contract: treat only fields returned by the tool as verified. Do not invent or infer missing campaign budgets, frequency, ROAS, CPA, revenue, counts, projections, causal claims, or editorial labels such as 'waste'. Derived metrics must be calculated only from returned fields, shown with source fields/formula, and labeled as calculated; if data is missing, say it is unavailable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesget_subscribers: List PostScript SMS subscribers with optional filters for email, phone, Shopify customer ID, and date ranges | get_subscriber: Get a single PostScript SMS subscriber by ID | get_keywords: List all active SMS opt-in keywords for the PostScript shop | get_keyword: Get a single PostScript SMS keyword by ID
paramsNoAction-specific parameters. get_subscribers: {page?: integer, sort?: string, email?: string, phone_number?: string, shopify_customer_id?: string, created_at_gte?: string, created_at_lte?: string, updated_at_gte?: string, updated_at_lte?: string} | get_subscriber: {subscriber_id: string} | get_keywords: none | get_keyword: {keyword_id: string}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them by disclosing the verified-provenance contract (15-minute window, any replica, source_path mapping) and the explicit data-accuracy contract about which fields count as verified and what must be labeled as calculated. That is genuinely useful behavioral context for a connector whose output feeds chart_render.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense paragraph where the majority of sentences govern chart_render behavior and response formatting rather than this tool. The purpose of the tool itself is buried in the first clause, and the reader must wade through cross-tool policy to find it.

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

Completeness3/5

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

The read-only, no-output-schema profile is adequately covered, and the provenance/accuracy rules are thorough. However, nothing explains the shape or scope of what the four actions return (list vs. single lookups, pagination for get_subscribers), leaving a gap the annotations and schema do not fill.

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%: the action enum and the nested params object already document every action and its fields inline. The description adds no parameter-level detail beyond what the schema provides, so the baseline 3 applies.

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

Purpose3/5

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

The opening clause names the domain and resources ('PostScript SMS marketing: subscribers, keywords, and shop analytics for Shopify merchants'), which distinguishes it from sibling connectors, but it never states an operation verb — the actual actions (get_subscribers, get_keyword, etc.) are only discoverable in the schema enum. An agent gets the topic but not what the tool does with it.

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?

The lengthy guidance is about the downstream chart_render workflow (provenance tokens, attribution footers), not about when to select this connector over alternatives or which action to pick for a given request. There is no stated condition for using this tool versus, say, klaviyo_connector or shopify_dashboard.

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

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