Ranksmile

One action

actions__get

Read-onlyIdempotent

One action of this workspace with what the user sees: overview, why (with its numbers), steps and which are done, the evidence read on the pages, the pages and prompts involved, the competitor pages behind it, and the content brief for owned actions.

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": {
      "workspace_id": "<workspace_id>",
      "action_id": "<action_id>"
    },
    "name": "actions__get"
  }
}

Input Schema

Name	Required	Description	Default
`action_id`	Yes	From actions__list.
`workspace_id`	Yes	From workspace__list.

Output Schema

Name	Required	Description	Default
`id`	Yes
`why`	No
`goal`	Yes
`brief`	No
`pages`	No
`steps`	Yes
`title`	Yes
`impact`	No
`status`	Yes
`prompts`	No
`surface`	No
`evidence`	No
`overview`	Yes
`competitor_evidence`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds only a catalog of returned payload sections (overview, why, steps, evidence, pages, competitor pages, brief), which is largely duplicated by the existing output schema, and says nothing about size, cost, or failure modes.

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 scope stated first and the payload enumerated after. The seven-item list is dense but each item conveys distinct returned data; nothing is redundant.

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 a rich annotation set, full schema coverage, and an output schema, the definition needs only orient the agent, which the payload summary does. It is complete enough to call correctly, though it omits any explicit relationship to actions__list.

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% and both parameters already state their provenance (actions__list, workspace__list). The description contributes no additional meaning about the parameters, so the baseline 3 applies.

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?

States it returns a single action of a workspace, which is clear and singular versus the plural sibling actions__list. The verb is implied by the name/title rather than stated, but the resource and scope are unambiguous.

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?

No explicit when-to-use, prerequisites, or routing to alternatives appears in the description; the only hint (action_id comes from actions__list) lives in the schema, not the text. An agent must infer that this is the detail-view counterpart to actions__list.

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

All Ranksmile tools Inspect

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

Need Help?