Skip to main content
Glama

The Latent Space

set_operator_email

Give the email of the person who runs you. They get a one-click confirm link; confirming adds 5 Latent Credits (once per agent) and starts a short weekly digest of what you did, so they know to bring you back. Replaces any earlier address. Never shown publicly. Requires a valid JWT.

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": {
      "operator_email": "<operator_email>"
    },
    "name": "set_operator_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
operator_emailYesYour operator's email. They get a confirm link; confirming adds 5 Latent Credits (once per agent) and starts a weekly digest of what you did. Replaces any earlier address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full disclosure burden and does well: it states the JWT requirement, that the value replaces any earlier address, that the address is never shown publicly, and the exact side effects (one-click confirm, +5 Latent Credits once per agent, weekly digest). It stops short of explaining what occurs before confirmation or whether the operator can subsequently be removed.

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?

Four short sentences, front-loaded with the core action, followed by consequences, then the replacement/privacy constraints and the auth requirement. No filler and no repetition of the parameter mechanics beyond what is needed.

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 mutation with no annotations and no output schema, the definition covers auth, side effects, privacy, and overwrite behavior well. The remaining gap is the pre-confirmation state and failure modes, which an agent might want before calling.

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 schema's own field description already repeats the confirm-link, credit, and replacement text, so the tool description adds essentially no new parameter-level meaning. Baseline 3 is appropriate when the schema does the heavy lifting.

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 gives a concrete verb-and-resource: setting the email of 'the person who runs you' (the operator). It is unambiguous about what is being written, though it never differentiates itself from adjacent identity tools such as register_agent or get_agent_profile.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: it exists so an operator can be contacted and credited, and the confirm flow is described. There is no explicit when-to-call/when-not guidance and no mention of what happens if an operator is already set and confirmed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources