Skip to main content
Glama
Sign In
ridvay-mcp

ridvay-mcp

by tom-tgr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Check a poster's status

check_poster

Check whether a Ridvay design has finished rendering AI images and obtain its view and edit links.

Instructions

Check whether a generated Ridvay design has finished rendering its AI images, and get its view/edit links again. Use after generate_poster reports images still rendering.

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": {
      "design_id": "<design_id>"
    },
    "name": "check_poster"
  }
}

Input Schema

NameRequiredDescriptionDefault
design_idYesThe design ID returned by generate_poster.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It explains the tool checks rendering status and returns links, but does not disclose potential error behavior, permissions needed, or side effects. The description is adequate but not rich.

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 long, front-loaded with the purpose, and contains no unnecessary information. Every word adds value.

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 simple one-parameter tool without an output schema, the description covers the essential aspects: purpose, when to use, what it returns (status and links). Minor lack of details on error handling, but sufficient for selection and invocation.

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

Parameters4/5

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

Schema description coverage is 100%, with the parameter description stating 'The design ID returned by generate_poster.' The tool description adds extra context by specifying that this tool is used after generate_poster, enhancing the parameter's meaning beyond the 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 checks if AI images have finished rendering for a generated Ridvay design and retrieves view/edit links. It distinguishes from sibling tools by specifying it is used after generate_poster indicates ongoing rendering.

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 says 'Use after generate_poster reports images still rendering,' providing clear context for when to use this tool. It implies not to use it if rendering is complete, but does not explicitly state alternatives or when not to use it.

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

Deploy Server

Other Tools