Skip to main content
Glama

mcphost

by dev.mcphost
OverviewDiscussionsAdmin

host.state.delete

Delete one key from this tenant's key-value state namespace.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesKey to delete from this tenant's key-value state namespace.
end_userNo"self" for the caller's own verified end-user identity, an explicit subject (only when this call carries no end-user identity of its own), or omit/null for the tenant-wide value.
tenant_keyNoThe key `signup` returned. Required only when this connection carries no Authorization: Bearer header -- when both are present, the header wins.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / end_user
      Added value: +{
+  "description": "\"self\" for the caller's own verified end-user identity, an explicit subject (only when this call carries no end-user identity of its own), or omit/null for the tenant-wide value.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / key / description
      Added value: +"Key to delete from this tenant's key-value state namespace."
  3. Added

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. While 'Delete one key' clearly expresses the mutation, it does not state whether deletion is permanent, what permissions or auth context are required, whether the operation is idempotent, or what response can be expected.

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 a single, front-loaded sentence with no filler or redundancy. Every word contributes meaning: 'delete,' 'one key,' 'tenant,' and 'key-value state namespace' all clarify purpose and scope.

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?

This is a simple tool with one required parameter and full schema documentation, so the description plus schema provide enough for a basic invocation. It is not perfect because the lack of annotations and output schema means the description does not convey response behavior, error semantics, or irreversibility, but the core call is adequately specified.

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 description coverage is 100%, so the schema already documents all three parameters, including key, end_user, and tenant_key. The description adds no parameter-level detail beyond restating the namespace scope, so the baseline of 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?

The description uses a specific verb and resource: 'Delete one key' in the host's key-value state namespace. It clearly distinguishes this from sibling host.state.delete_rows by emphasizing single-key scope, and the tenant-scoped wording adds useful precision.

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

Usage Guidelines2/5

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

There is no guidance about when to use this tool versus alternatives such as host.state.delete_rows, host.state.set, or host.state.query. The single-key qualifier implies a contrast with delete_rows, but no explicit usage conditions, exclusions, or alternative recommendations are provided.

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

All mcphost toolsInspect
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.

Resources