detach_variableStop exposing a variable to a site's Worker env. Takes effect on the site's next function deploy.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | variable name to detach | |
| slug | Yes | owned site slug |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations note destructiveHint=true; description adds crucial timing detail 'Takes effect on the site's next function deploy' beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences with no wasted words. Action verb first, then effect timing.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-parameter tool with output schema and annotations, description covers the key behavioral aspect (detach and deploy timing). Nearly complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and both parameters are well-described. Description adds no extra meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses specific verb 'stop exposing' and resource 'variable to a site's Worker env', clearly distinguishing from sibling tools like attach_variable and delete_variable.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidelines for when to use this tool versus alternatives like delete_variable or set_variable. Usage is implied but not clarified.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Many tools have overlapping purposes (e.g., add_domain, add_subdomain, add_custom_domain, add_sending_domain) or similar names like check_domain and check_custom_domain, which can confuse an agent. While descriptions help, the sheer number of closely related tools makes it difficult to consistently select the correct one.
Most tools follow a verb_noun pattern, but there are exceptions like 'read_thread' (instead of get_thread) and 'mark_thread_read' (verb_noun_verb). Prefixes like 'data_' are used inconsistently with other tools, but overall the naming is still readable.
With 103 tools, the server is extremely bloated. Even for a comprehensive platform, this count overwhelms any agent and makes the tool surface difficult to navigate. Many tools could be merged or are too granular.
The toolset covers a wide range of operations across sites, domains, email, marketplace, projects, contracts, and functions. While some updates (e.g., general contract editing) are missing, the surface is mostly comprehensive for the domain.