Skip to main content
Glama

Eveoy — Verified In-Store Foot Traffic ($24.99/customer)

by com.eveoy

Subscribe to the Eveoy newsletter

subscribe_newsletter
Idempotent

Subscribe an email address to the Eveoy newsletter (case studies + lookbooks).

Use this when the user EXPLICITLY asks to subscribe or sign up for updates.

Trigger phrases include: "subscribe me", "sign me up for the newsletter", "add my email to updates", "join the Eveoy list".

Returns: { ok: true }.

Do NOT use this for: anything other than an explicit newsletter opt-in. Always confirm the email with the user before calling — this writes data.

Cost: free. Latency: fast. Writes data (creates a subscription). Confirm first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYesEmail to subscribe to the Eveoy newsletter.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate it writes data (readOnlyHint=false) and is idempotent. Description adds that it creates a subscription, is free, fast, and requires confirmation. No contradictions.

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?

Well-structured with clear sections and bullet points. Front-loaded purpose. Slightly verbose but still efficient.

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

Completeness5/5

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

For a simple tool with one parameter and no output schema, the description covers purpose, usage, behavioral notes, and return value completely.

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 full email description. The description adds no extra parameter meaning beyond the schema's own description.

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?

Clearly states it subscribes an email to the Eveoy newsletter (case studies + lookbooks). Distinct from siblings as the only subscription tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to use only when user asks to subscribe, lists trigger phrases, and states not to use for other purposes. Instructs to confirm email before calling.

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

All Eveoy — Verified In-Store Foot Traffic ($24.99/customer) toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: information lookup, booking, pricing, checkout, order status, etc. No two tools overlap in functionality; descriptions clearly delineate boundaries.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with underscores (e.g., ask_eveoy, get_pricing, start_checkout, list_industries). No mixing of conventions.

Tool Count5/5

11 tools cover the full customer journey for a sales platform without being excessive. Each tool serves a specific, necessary function and fits within the typical 3-15 range.

Completeness4/5

Core workflows (information, pricing, checkout, order status, demos, human handoff) are covered. However, the ask_eveoy tool refers to a non-existent 'search_directory' tool, indicating a minor gap in the tool surface.

Resources