Skip to main content
Glama

report_mcpize_link

Check the MCPize subscription status and payment tier for a given DataNexus tool ID. Returns if the tool is free, needs subscription, or not configured.

Instructions

Returns the MCPize subscription status and payment tier for the current DataNexus API key. Read-only. No side effects. Idempotent. tool_id: DataNexus tool identifier to check (e.g. "T01", "T07", "T10") — pass the ID of the tool the user is asking about; unknown or test values always return a structured response, never raise an exception. Output fields: status (str) — "free" (tool is in free window, no subscription needed), "subscription_required" (paid MCPize plan required, see upgrade_url), or "not_configured" (payment active but tool not yet listed on MCPize); message (str) — human-readable explanation; tool_id (str) — echoes the input; upgrade_url (str) — MCPize checkout URL, present only when status="subscription_required". Example free-window response: {"status": "free", "message": "This tool is currently in its free window. No subscription required.", "tool_id": "T10"}. Example paid response: {"status": "subscription_required", "message": "A subscription is required to access this tool.", "upgrade_url": "https://mcpize.com/checkout/...", "tool_id": "T10"}. Call this when the user asks about their subscription, plan tier, usage limits, or billing status. Do not call this to validate data quality — use validate_tool_output or report_feedback for data issues. If this tool's response does not serve the user's need, call report_feedback with feedback_type="agent_gap", tool_id="report_mcpize_link", intended_query="{what the user needed}", gap_description="{what was missing or wrong in the result}".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tool_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Discloses read-only, no side effects, idempotent behavior. Describes response structure, example outputs, and handling of unknown tool IDs. No annotations provided, so description fully compensates.

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?

Front-loaded with core function, but includes detailed output examples and fallback instructions that, while useful, make it longer than necessary. Still, every sentence earns its place.

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

Completeness5/5

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

Given the simple single-parameter tool and presence of output schema (though not provided in input), description fully covers purpose, usage, behavior, and fallback. No gaps remain for an agent to determine correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has no description for 'tool_id'. Description adds examples ('T01', 'T07', 'T10'), clarifies it's the user's tool of interest, and explains behavior for unknown/test values (never raises exception). Adds significant value beyond schema.

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

Purpose5/5

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

The description clearly states the tool returns MCPize subscription status and payment tier for the current API key. It specifies the action, resource, and context, distinguishing it well from sibling tools which cover unrelated domains.

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

Usage Guidelines5/5

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

Explicitly states when to call (for subscription/plan/billing queries) and when not to (data quality issues), directing to sibling tools. Also provides fallback instructions via report_feedback.

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/datanexusmcp/mcp-server'

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