Skip to main content
Glama
Sign In

Perfect Venue MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Send proposal in Perfect Venue

perfect_venue_send_proposal
Read-onlyIdempotent

Send proposal in the user's own Perfect Venue account from ChatGPT, Claude or any AI agent. Returns how to do it in Perfect Venue step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Perfect Venue Cloud Browser. Perfect Venue's official API: Perfect Venue has one public API, the Leads API: a write-only endpoint that creates a lead from your own contact form, and only on the Enterprise plan (checked 11 Oct 2026).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "perfect_venue_send_proposal"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and non-destructive behavior; the description adds that the tool opens nothing by itself and returns screens/buttons/fields, which is important behavioral context. It also discloses the API limitation, though it does not detail output format beyond the step list.

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?

The description is three sentences and mostly front-loads the key clarification, though the first sentence's 'Send proposal' framing is less precise than the second sentence. The API context is relevant but could be trimmed.

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 zero-parameter, read-only guidance tool with annotations covering safety, the description provides enough context: what it returns, that it does not act, and which tools to use next. No output schema exists, so the step-by-step return is adequately described.

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?

There are zero parameters, so the schema imposes no semantic burden; the description appropriately does not discuss parameters. Baseline 4 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?

The description identifies the resource (Perfect Venue proposal) and clarifies that the tool returns step-by-step instructions rather than performing the send, which distinguishes it from the cotlet_browser_* execution tools. The opening 'Send proposal' phrasing is slightly misleading for a read-only guide, but the second sentence corrects it.

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?

It explicitly says to use this tool to get the steps and then use cotlet_browser_* tools in the Cloud Browser to actually perform the action. It also notes the official API limitation, which explains why browser automation is needed, though it does not name a direct alternative for proposal sending.

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

All Perfect Venue MCP Server and API by Cotlet 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