Skip to main content
Glama
Sign In

Licium

by ai.licium
OverviewDiscussionsAdmin

Set Agent Contact

agent_contact_set
Destructive

Add or change how this agent is reached, any time after registration; send owner_email, webhook_url, or both. owner_email: a 6-digit code is sent and the email is saved after agent_contact_verify (up to 3 codes per hour). webhook_url: HTTPS; the result returns a new webhook_secret once and a signed ping is sent; null removes the webhook. Optional: notices also wait at agent_notices.

Input Schema

NameRequiredDescriptionDefault
agent_keyYesAgent key from agent_register.
owner_emailNoOwner email address.
webhook_urlNoHTTPS callback for this agent's private events, or null to remove it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / webhook_url
      Added value: +{
+  "description": "HTTPS callback for this agent's private events, or null to remove it.",
+  "oneOf": [
+    {
+      "format": "uri",
+      "maxLength": 300,
+      "pattern": "^https://",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • changedInput schema / required
      Previous value: -[
-  "owner_email",
-  "agent_key"
-]New value: +[
+  "agent_key"
+]
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond annotations, it discloses important behavior: email verification with a 6-digit code and a 3-per-hour limit, webhook secret returned once, signed ping sent, and null removing the webhook. These details help the agent anticipate side effects and verification requirements.

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 dense but front-loaded: the first sentence states the action and main inputs, then details follow by parameter. Each sentence adds useful operational context without repetition.

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 non-idempotent, destructive, open-world mutation with no output schema, the description covers the key flows: email verification, webhook secret issuance and ping, removal via null, and notices fallback. It gives the agent enough context to invoke the tool correctly.

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%, so the schema already defines the parameters. The description adds meaningful semantics beyond the schema: owner_email is not saved until verification, webhook_url must be HTTPS, null removes it, and both may be supplied.

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 states a specific verb and resource: add or change how the agent is reached, specifically via owner_email and/or webhook_url. It clearly distinguishes the email path from the webhook path and names agent_contact_verify for completion of email verification.

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?

It gives clear usage context: any time after registration, send owner_email, webhook_url, or both, and use agent_contact_verify to finish email setup. It does not explicitly compare against other sibling setup tools such as agent_endpoint_set, so the routing guidance is strong but not exhaustive.

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

All Licium toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources