OneLence

Goal and funnel settings

onelence_get_measurement

Read-onlyIdempotent

What a site optimizes for (revenue, conversions or visitors) and how its funnel is set up: each step, the event it counts and whether the funnel is the site's own, the workspace default or OneLence's. Use it to explain onelence_get_funnel numbers or before changing tracking.

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": "onelence_get_measurement"
  }
}

Input Schema

Name	Required	Description	Default
`site`	No	Site domain (e.g. example.com) or site id. Defaults to the workspace's newest active site.

Output Schema

Name	Required	Description	Default
`site`	Yes
`funnel`	Yes
`object`	Yes
`analytics_goal`	Yes
`analytics_goal_set`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the lower bar applies; the description adds valuable domain behavior by disclosing that funnel ownership can be the site's own, the workspace default, or OneLence's — an inheritance nuance not visible in the schema or annotations. It does not add rate limits or error behavior, but the output schema covers return shape.

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?

Two sentences, front-loaded with the resource definition and followed by usage, with no filler. The first sentence is dense with nested clauses but still parses cleanly.

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 single-parameter, read-only introspection tool with an output schema, the description covers purpose, inheritance semantics, and when to call it. Nothing critical is missing, though naming related configuration tools for the 'before changing tracking' case would close the loop.

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% and the single 'site' parameter already documents the domain-or-id format and the newest-active-site default. The description only refers to 'a site' generically and adds no syntax or selection meaning beyond the schema, so the baseline 3 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?

States a precise resource: the site's optimization goal (revenue, conversions, visitors) plus its funnel configuration, step events, and funnel ownership. It implicitly distinguishes itself from onelence_get_funnel by framing this tool as the settings behind those numbers, so an agent can separate the two without opening either schema.

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?

Gives two explicit use cases: explaining onelence_get_funnel figures and checking configuration before changing tracking. That is clear context plus a named sibling, but it omits explicit when-not-to-use guidance or a pointer to the mutation tools (e.g. save_event_definition) that would follow 'before changing tracking'.

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

All OneLence tools Inspect

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.