Skip to main content
Glama

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

by com.eveoy

Get the Eveoy app

get_app_link
Read-onlyIdempotent

Get the link to download the Eveoy shopper app (iOS / Android).

Use this when the user wants to:

  • Download or install the Eveoy app

  • Become an Eveoy shopper

  • Find the app store link

Trigger phrases include: "get the eveoy app", "download eveoy", "how do I become a shopper", "app store link", "install the app".

Returns: { url, platforms, notes }. Returns the canonical get-app page, which routes to the correct store per device.

Do NOT use this for: brand/business questions (use ask_eveoy) or pricing (use get_pricing).

Cost: free. Latency: <50ms. Read-only. Idempotent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
notesYes
platformsYes

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds cost (free), latency (<50ms), and return shape (url, platforms, notes), further clarifying behavior without contradicting annotations.

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?

Concise and well-structured, with front-loaded purpose and bulleted lists for uses and non-uses. Every sentence adds value with no redundancy.

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?

Given no parameters, good annotations, and an output schema, the description is fully complete: it explains return fields, use cases, exclusions, and performance characteristics.

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?

No parameters exist; schema coverage is 100%. The description does not need to add parameter semantics, so baseline score of 4 is appropriate.

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 explicitly states the tool provides a link to download the Eveoy app, with specific verb+resource. It distinguishes from siblings like get_pricing and ask_eveoy by stating what it does not do.

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?

Clearly lists when to use (download/install/becoming shopper/app store link) and when not to use (brand/business questions and pricing), with explicit sibling references. Includes trigger phrases for easy matching.

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