Skip to main content
Glama
Sign In

venumark

by com.venumark
OverviewDiscussionsAdmin

get_signup_link

A direct VenuMark signup link for the human to open in their browser. role 'venue' is for organizers who run vendor applications; optional tier ('growth' or 'pro') and cadence ('month' or 'year') preselect the plan, and checkout completes in the browser via Stripe. role 'vendor' is for food trucks and caterers (free forever). Event creation and applications happen in the web app after signup.

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": {
      "role": "<role>"
    },
    "name": "get_signup_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYesWho is signing up
tierNoOptional paid tier to preselect (venues only; omit for Free)
cadenceNoOptional billing cadence for the preselected tier

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden. It explains that the tool returns a link for the human to open, checkout happens via Stripe, and event creation occurs later. It does not mention any side effects or restrictions, but for a simple link retrieval, the behavior is sufficiently transparent.

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 concise, with the purpose stated upfront in the first sentence followed by two sentences detailing roles and optional parameters. No unnecessary words, and the structure is effective.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has no output schema, so the description should detail the return value. It mentions 'a direct VenuMark signup link' but does not specify the format (e.g., URL string). It covers the signup flow but lacks explicit output semantics, leaving some ambiguity.

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 coverage is 100% with brief descriptions. The description adds value by explaining that 'venue' is for organizers, 'vendor' for food trucks, and that 'tier' and 'cadence' are optional and only for venue. It provides examples and clarifies preselect functionality.

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 it provides a signup link, explains the two roles ('venue' and 'vendor'), and distinguishes their purposes. It uses specific verbs ('get') and resource ('signup link'), and adds detail about what each role does.

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 explains when to use with each role and mentions optional parameters for venue. However, it does not explicitly state when not to use this tool or provide alternatives like other sibling tools, but the context is clear given no sibling serves a signup purpose.

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

All venumark 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