Skip to main content
Glama

marketinque — launch plan & backlink index

by com.marketinque
OverviewDiscussionsAdmin

One step in full

get_step
Read-only

One plan step in full: title, detail, the target URL where it happens, the play it follows, the prerequisite slugs and whether they are met (unlocked), how it verifies (self, evidence URL or an automatic signal), minutes and cost. Read it before working a step that next_steps or get_plan returned; the slug comes from those. Read-only; no side effects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
doneNoStep slugs already done — the "done" list of marketinque.json. Free tier only; a project's own ticks are used instead and this is ignored.
slugYesThe step slug exactly as get_plan or next_steps returned it, e.g. "p2-dest-alternatives".
traitsNoProduct traits that decide which steps apply (b2b, b2c, ai-native, dev-tool, no-code, mcp, has-integrations, eu-traffic, mobile-app); omit for the generic plan. Free tier only; a project's saved traits are used instead.
not_applicableNoStep slugs the founder ruled out — the "not_applicable" list of marketinque.json. Free tier only; ignored for a project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / done / description
      Added value: +"Step slugs already done — the \"done\" list of marketinque.json. Free tier only; a project's own ticks are used instead and this is ignored."
    • addedInput schema / properties / not_applicable / description
      Added value: +"Step slugs the founder ruled out — the \"not_applicable\" list of marketinque.json. Free tier only; ignored for a project."
    • changedInput schema / properties / slug / description
      Previous value: -"The step slug, e.g. \"p2-dest-alternatives\"."New value: +"The step slug exactly as get_plan or next_steps returned it, e.g. \"p2-dest-alternatives\"."
    • addedInput schema / properties / traits / description
      Added value: +"Product traits that decide which steps apply (b2b, b2c, ai-native, dev-tool, no-code, mcp, has-integrations, eu-traffic, mobile-app); omit for the generic plan. Free tier only; a project's saved traits are used instead."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already provide readOnlyHint: true, and the description reinforces this with 'Read-only; no side effects.' It adds context that this is a safe read operation, and explains what data is returned. No contradictions; the additional phrase 'no side effects' is redundant but consistent. The description does not cover edge cases like invalid slugs, but that is minor given the annotation coverage.

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

Conciseness5/5

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

The description is two sentences, front-loading the purpose and content, and then the usage context. Every word is purposeful, with no filler. It is concise and well-structured.

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 tool with 100% schema coverage and no output schema, the description adequately covers what the tool returns and when to use it. It does not discuss error handling or edge cases, but these are not critical for a simple read operation. The description is complete enough for an agent to correctly invoke the tool.

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 parameters are already documented with descriptions. The tool description itself adds little about parameters beyond the schema, though it reiterates that the slug comes from get_plan or next_steps, which is already in the schema. This meets the baseline for 100% coverage but does not add extra value.

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's function: returning one plan step in full, and enumerates the specific fields returned (title, detail, URL, play, prerequisites, verification, minutes, cost). It distinguishes itself from siblings by explicitly mentioning it is used after next_steps or get_plan, and the slug source is from those tools. The purpose is precise and unambiguous.

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

Usage Guidelines4/5

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

The description explicitly tells when to use the tool: 'Read it before working a step that next_steps or get_plan returned' and states the slug comes from those tools, providing clear usage context. It does not explicitly mention when not to use it or alternative tools, but the context is strong enough for an agent to decide.

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

All marketinque — launch plan & backlink index 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