Skip to main content
Glama

Visibility Genies

Read an action

get_action
Read-only

Read one saved action with its steps, pages, due day, notes and change history, each change saying whether it was made on the Actions page, by your agent or via Genie. Uses no credits or provider calls.

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": {
      "projectId": "<projectId>",
      "id": "<id>"
    },
    "name": "get_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe action's id from list_actions.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.

Output Schema

NameRequiredDescriptionDefault
metaNo
notesYes
actionYes
changesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely non-structured context: no credits consumed, no provider calls, and that each change record carries provenance (Actions page, agent, or Genie) — useful for interpreting the response.

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 no filler; the field enumeration earns its place by telling the agent what comes back. Slightly dense but efficient.

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 annotations, full schema coverage and an output schema, the description covers what an agent needs: what it returns, its cost profile, and where the id comes from. Only explicit sibling routing is absent.

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 coverage is 100%, with both id and projectId documented including a pointer to list_projects and the billing implication. The description adds nothing beyond that, so baseline 3 applies.

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?

States a specific verb and resource ('Read one saved action') and immediately enumerates the payload: steps, pages, due day, notes, change history. The singular 'one' contrasted with 'list_actions' in the schema makes the scope unambiguous against sibling list tools.

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?

The description implies the read-a-single-record use case and the schema's reference to list_actions suggests where ids come from, but there is no explicit when-to-use/when-not guidance and no named alternative for retrieving many actions or their edits.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources